chrisbra80

23 ms·

1.
by chrisbra80 2mo ago
> 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 he
2.
by chrisbra80 7mo ago
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.
3.
by chrisbra80 7mo ago
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
4.
by chrisbra80 7mo ago
Oopps, missed that. Now there is a v9.2.0 tag and a v9.2.0000 tag
5.
by chrisbra80 7mo ago
It still does, but those only work with a Vim built that has those interfaces compiled in.
6.
by chrisbra80 2y ago
Vim implemented this: `:call err_teapot()`.
7.
Google Groups decided to block the Vim-dev mailinglist
9 points by chrisbra80 2y ago|0 comments
8.
by chrisbra80 7y ago
what are you missing? Please use the issue tracker for discussions of better features.
9.
by chrisbra80 7y ago
I am open for suggestions on how to make the search work better.
10.
by chrisbra80 7y ago
Haha, thank you! (I am the author)
11.
by chrisbra80 7y ago
that wasn't there, when I noticed the commit
12.
Vim 8.2(vim.org)
104 points by chrisbra80 7y ago|75 comments
13.
by chrisbra80 11y ago
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 proble