2 ms·
The LSP, treesitter parsing, debug protocol etc. are good developments, but everything else in neovim is just way different from VSCode. And the vim modal edit
by zozbot234 4y ago
The LSP, treesitter parsing, debug protocol etc. are good developments, but everything else in neovim is just way different from VSCode. And the vim modal editing pattern is nice for a basic text editor but has pretty poor extensibility compared to a menu-driven program - at some point you just can't do everything with single letters, you need actual, complex commands. So a real T-Vision/TUI conversion of VS Code might still be very worthwhile.
- alwillis 4y agoAnd the vim modal editing pattern is nice for a basic text editor but has pretty poor extensibility… Nothing could be further from the truth. There are tons of plugins, scripts, tutorials for literally every scenario you can imagine since Vim has (never mind its predecessor Vi) has been around since 1991. at some point you just can't do everything with single letters, you need actual, complex commands Vim’s power is its composability. Once you understand text objects (word, sentences, paragraphs) and motions, you can do anything you want. If you need to repeat a string of commands together, you can record macros on the fly, create an autocommand or a plugin if that’s what needed. Neovim in particular has LSP support built-in, which gives the editor semantic knowledge of your code, just like an IDE. So renaming, refactoring, formatting, syntax highlighting work better. There’s even a LSP server for Free Pascal:https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#pasls https://github.com/neovim/nvim-lspconfig/blob/master/doc/ser....