News for hackers. Stuff that matters.

chrisbra80

Re:Codex Security on Wednesday July 29, 2026 @05:24AM (#49095130)
> If you're an open-source maintainer, you can apply for conditional Codex Security access here:

> https://openai.com/form/codex-for-oss/

Hey, Lead maintainer of vim here. Applied twice already never heard anything back. This is a frustrating experience!

Re:Vim 9.2 Released on Sunday February 15, 2026 @12:02PM (#47025289)
I admit I am guilty of that, although I ran it via several iterations to make sure it covers everything I needed and created a nice style that i liked. It just saves me so much time.
Re:Vim 9.2 Released on Sunday February 15, 2026 @12:00PM (#47025271)
I suppose people not familiar with Vim version numbers may try tag v9.2.0 instead of using v9.2.0000, so for those I added a shortcut
Re:Vim 9.2 Released on Saturday February 14, 2026 @01:36PM (#47017049)
Oopps, missed that. Now there is a v9.2.0 tag and a v9.2.0000 tag
Re:Vim 9.2 Released on Saturday February 14, 2026 @01:26PM (#47016947)
It still does, but those only work with a Vim built that has those interfaces compiled in.
Re:418 I'm a Teapot on Monday October 28, 2024 @05:21AM (#41969162)
Vim implemented this: `:call err_teapot()`.
what are you missing? Please use the issue tracker for discussions of better features.
I am open for suggestions on how to make the search work better.
Haha, thank you! (I am the author)
Re:Vim 8.2 on Thursday December 12, 2019 @11:57AM (#21773594)
that wasn't there, when I noticed the commit
Re:Vim is moving to GitHub on Wednesday March 25, 2015 @05:09PM (#9265929)
1) Here the real problem is the maintainer of the syntax file who is hard to reach. I have contacted him several times but never got fa reply. No real problem of Vim. 2) merged February 25th. Not bad I would say (again a runtime file problem) 3) merged with 7.4.646 4) yes, sometimes it takes a while. 5) took long but has been merged with 7.4.652