vim-local-history
lsp-format-modifications.nvim
| vim-local-history | lsp-format-modifications.nvim | |
|---|---|---|
| 2 | 4 | |
| 33 | 139 | |
| - | 0.7% | |
| 10.0 | 2.5 | |
| over 4 years ago | 11 months ago | |
| Python | Lua | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vim-local-history
-
Auto formatting in shared repo's/projects
There is a similar nvim plugin, but I'm not sure if it is still compatible: https://github.com/dinhhuy258/vim-local-history
-
Why LSP?
Didn't realize I was talking to the person who worked both on IntelliJ Rust and rust-analyzer!
This is the best case I've ever heard for IDEs. Thank you!!
1 and 3 seem to me to require extensions/improvements to the LSP protocol.
2, and 6 seem like one could build them off of treesitter (but I don't think anyone has as of yet).
5 seems already implemented in a vim plugin[0].
Thanks for 4 and 7 (the "myriad of small, polished details") also, I feel like I have to spend a week using an IDE to get a feel for them.
[0] https://github.com/dinhhuy258/vim-local-history
lsp-format-modifications.nvim
-
Can the null-ls formatter be configured to automatically format only new code, and leave existing code alone?
I’ve been using the plugin lsp-format-modifications to format only modified text regions. Haven’t tried it with Python black though so would be worth testing it out yourself :)) There’s a note at the bottom of the README about how to set it up with null-ls :)
-
Format selection instead of entire file?
Tangentially related: if you're specifically interested in formatting modifications (which is often the case when folks are trying to format a specific range of lines) check out lsp-format-modifications.nvim.
-
Auto formatting in shared repo's/projects
I think you’re referring to my plugin, lsp-format-modifications.nvim. It uses the diff from Git/Mercurial’s point of view to establish what should be formatted. For the actual formatting, it uses Neovim’s built-in LSP formatting via vim.lsp.buf.format by default.
- lsp-format-modifications.nvim: LSP formatting, but only on modified text regions
What are some alternatives?
trouble.nvim - 🚦 A pretty diagnostics, references, telescope results, quickfix and location list to help you solve all the trouble your code is causing.
nvim-lspconfig - Quickstart configs for Nvim LSP
typescript-lan
formatter.nvim
ncm2 - :heart: Slim, Fast and Hackable Completion Framework for Neovim
darker - Apply black reformatting to Python files only in regions changed since a given commit. For a practical usage example, see the blog post at https://dev.to/akaihola/improving-python-code-incrementally-3f7a