Will this plugin become obsolete with Neovim v10? #234
Comments
|
I don't think you need to install this plugin for Neovim. However, this plugin is still useful for Vim and is not considered obsolete. After all, this is a "Vim" plugin :) |
|
Would it maybe make sense to add an overview in the readme that explains which versions of Vim and Neovim need this plugin and which don't? And also (if that's a thing) which EditorConfig features might be unavailable when using the built-in support versus when using the plugin? |
|
A version of this plugin (e014708 from 2023-08-07) comes bundled with Vim since 9.0.1799, see vim/vim#12902. A Lua EditorConfig implementation comes bundled with Neovim since 0.9, see neovim/neovim@ab9a2c4. It supports all properties currently in the wiki, including |
|
@scy Please check out #223 (comment) . While Vim now includes this plugin, the development still happens in this repo. |
|
@xuhdev Yes, I didn't disagree with that. My suggestion was to add a short section to the readme that explains to people who arrive at this repo whether they need to install it or whether their version of (Neo)Vim already comes with it. |
Based on my research in <editorconfig#234 (comment)>.
Based on my research in <#234 (comment)>.
|
Now clarified in README |
Parsing and interpretation of `.editorconfig` files comes bundled into vim and nvim according to this: editorconfig/editorconfig-vim#234 (comment)
Hello, this is a question, not a bug.
Will
editorconfig-vimbecome obsolete for users of Neovim now that version 10 will have EditorConfig recognition and application included?The text was updated successfully, but these errors were encountered: