111–120 of 220 posts
Neovim is such a weird derivative utility to me. Derivative/forked software usually isn't very successful to begin with, but then Neovim makes attempts to be modern and it's so not appealing at all. Here are some 5 second examples. Example 1: nvim . Still uses Netrw, which is fine, but doesn't even attempt to do things like: let g:netrw_preview=1 let g:netrw_banner=0 let g:netrw_browse_split=4 let g:netrw_liststyle=…
Earlier quoted context omitted.
What do you mean by "terminal sessions"? I use vim inside regular xterms or tmux. Am I using such terminal sessions already? What would be different in nvim?
Both vim and neovim have the ability to open a terminal in a window split. It's not my preferred workflow but some people really like it rather than tmux or ctel-z to drop onto a shell... the implementation of this feature in neovim is a lot nicer than the one in vim. One thing i do use it for: In neovim there's options to open the terminal as a sort of overlay on top of the existing splits, they call it floating ter…
Earlier quoted context omitted.
The debugger. I made your same argument for years to a buddy of mine that always used WebStorm (I'm a Python dev and he kept pushing me to try PyCharm). A coworker pushed me to try PyCharm since we're on Windows and I haven't really looked back. I even bought CLion. If you can point me to an easy debugger to set up in neovim I'd probably be right back, but I can't. Couldn't figure out how to set up vimspector. And in…
Debugging in Neovim is quite simple, I recommend nvim-dap, I made a few videos: https://youtu.be/ga3Cas7vNCk https://youtu.be/SIYt1dopfTc If you prefer Vimspector: https://youtu.be/-AZUIL1rY3U
Thank you David, they're a fantastic overview of these plugins!
People who have tried both vim and nvim: - I have a theory that using `coc.nvim` is still the superior solution even compared to a native LSP. Why? Cause we can siphon from the huge man-hours of development and polish that M$ has put on VSCode. Every time they tweak VSCode, we at downstream, enjoy the benefits. Am I wrong in my assessment? - Vim's regexp-based syntax highlighting is annoying. So I think nvim+tree-sit…
I came from coc.nvim and switched to the native LSP when it was released on nightly. For a while I was using VSCode and came back to nvim and switched back to coc.nvim. I found that the native LSP's community to be too quickly changing. Plugins that were necessary earlier weren't, while new necessary plugins came into play. But, coc.nvim was steady chugging along and my old settings file worked out of the box. I'm al…
Earlier quoted context omitted.
Thanks for summarizing the highlights! The client-server part is the one I'm most excited about. It is one of my favorite things in kakoune and it'll be nice to have it on neovim too. I find it more intuitive to use separate terminal windows with all the usual window manager shortcuts, instead of using vim-specific terminal splits.
Do the kakoune and neovim keyboard shortcuts conflict for you? I've put off trying non-vim modal editors because I think there's only enough room for one set of shortcuts in my head. How difficult is it for you to switch between them?
Earlier quoted context omitted.
There's 0 configuring. It's as simple as installing one of the many LSP clients, like ALE, that will automatically detect and start a language server for you with the right arguments.
If that's true, I'd really like to try that. I've never heard of ALE, so thanks for that. Still, the fact is that you have to know what to install. It's not like the NeoVim manpage mentions any LSP clients. So it requires a lot of tinkering, reading and participating in the community to figure out how to do stuff. That's exactly opposite of 0-configuring. If NeoVim could bundle an LSP client with it, and have a confi…
https://paste.sr.ht/~mjlbach/1a1df5cd61627e87ea4c4355a0473bf...
Earlier quoted context omitted.
I do recommend that new users just use coc.nvim, but not exactly because of what you said. Both coc.nvim and the built in LSP implementation use basically the same Language Servers, so whatever updates happen to the server will benefit either approach. However, coc.nvim DOES have a large community that has built a neatly packaged LSP client framework (and many other tie-ins like completion, snippets, formatting, and…
If you have ever said the word "bloat" unironically on your computer with 64G of RAM, built in might be for you. I really just want one config that works on: * Yes, my Ryzen 5 with 32G of RAM * My Pinebook Pro with 4G of RAM (and like 3.7G accessible) (and limited storage as well) * My jump host / gateway VM with 512MB of RAM (and even more limited storage than the PBP) So pulling down and running node.js to use coc.…
lua is such a nice and sane language for application config. I really enjoy neovim's choice to use it, and with this release more or less allow 100% of typical configuration to be done entirely in lua. Good riddance to bespoke scripting languages.
One of the appealing things about Neovim has always been > MessagePack structured communication enables extensions in any language Is anyone writing extensions in other languages? Does it work well?
Earlier quoted context omitted.
True, it was like half a day of extensive coding for the basics, a bit of cursing, then about two weeks of settling in and then a few hours over a couple of months, when I did heavy extension and configuration. Bonus: my window manager has similar keybindings these days
Yes, do it this way. When I learned vim, I just went to work and decided to use it one day. The only thing I did was get on Stack Overflow and look up how to turn off the arrow keys, so I would have to use hjkl. As you said, by the end of the workday I was very comfortable with basic vim use.