Gregory Anders

Note that with https://github.com/neovim/neovim/pull/26618, https://github.com/neovim/neovim/pull/26193 is no longer a breaking change. Plugins should still migrate to the new configuration format, but there is no immediate need to do so.

Here is a patch for the docs: ```diff diff --git a/runtime/doc/filetype.txt b/runtime/doc/filetype.txt index deb947cf1..feb946252 100644 --- a/runtime/doc/filetype.txt +++ b/runtime/doc/filetype.txt @@ -829,6 +829,12 @@ The mappings can be disabled with: >...

> But there is also the matter of the zig_std_dir, which I would like to remove because it also seems intrusive. But I do not even know fully what its...

> Ok, seems good to me, but is the implementation good enough? @habamax pointed out > > > On windows gvim system() call looks ugly and you probably don't want...

@chrisbra The original implementation (upstream) has a `system()` call (`system('zig env')`). The question was (I believe) whether this should be preserved or removed.

>Just document that `g:zig_std_dir` can be set by `system('zig env')` in a custom filetype auto command Specifically, the `std_dir` field from the output of `zig env`. If we want a...

I know this is an old issue, but just wanted to point out that the linked instructions in the DKMS README helped me. I was unable to get xpadneo working...

>but jj users already suffer this and have to configure their editors (such as to support the JJ: comments), so probably less of a problem. Tangential, but both Vim and...

>How can a user give up if they're constantly bombed with $EDITOR opening? `git rebase --interactive` stops if the editor returns a non-zero exit code. This can be done in...

Closing per https://github.com/neovim/neovim/issues/28476#issuecomment-2074885532. As mentioned in that comment, the original justification for this proposal does not seem to be accurate.