Long live simple, non-proprietary, open editors which can be extended infinitely: Emacs & Vim (and their derivatives) FTW.
Neovim 0.8 Released
201–210 of 230 posts
Re: Neovim 0.8 Released
#202I've tried using neovim for C++ dev but keep ending back in either vscode with intellisense or YCM on Vim. I don't know if I'm just misconfiguring things but I haven't been able to get autocomplete working correctly. Any tips?
You'll need to configure clangd or ccls correctly with neovim's lsp, which in turn requires your build chain to be clean. It's definitely a huge time sink. Feel free to email me if you have specific issues!
It (mostly) worked out of the box in another project with only some minor quirks though
Re: Neovim 0.8 Released
#203Earlier quoted context omitted.
I don't want MS to monitor me. Anything that enables them to track me better is sensitive because I don't want to be monitored.
No one stops you from using VSCodium. But associating a software with spyware (a black/white action) should not but tied to how much telemetry (a spectrum) they collect. It's about what type of data they collect and what they do with the data. If they deliberately use that data to cause any damage (black/white), you can call it spyware. But if they only use that to improve their software, no, you shouldn't.
Re: Neovim 0.8 Released
#204I feel the proliferation of plugins has made the whole vim/neovim echo system too complicated and overwhelming to adapt for a new user. 1. Vim itself has a learning curve 2. There are many great plugins, but if they don't work for you, then unless you are an advanced user, it is impossible to get everything working without wasting a day 3. I find it weird that to get a vim plugin to work, I might have to install llvm…
I don't know why but even if I install same plugins with same config on various machines of same Linux distro version, some just throw errors on every launch while others tend to work and it's getting to the point of annoyance to keep using it.
It does feel like it's piling up parts hoping they don't fall apart.
Using vs code with remote config does make it feel saner.
Re: Neovim 0.8 Released
#205If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ , or new native GUI editors like https://zed.dev/ ? It's impressive to see what the Neovim community has built — preconfigured setups like https://nvchad.com/ are especially wild. But it still feels like a huge amount of work, hoop jumping, and _fragility_ just to reach parity with V…
I also use vscode and other IDEs. Why make it seem like one has to choose? That's like saying 'why do you use a hammer, i like screwdrivers better'.
Re: Neovim 0.8 Released
#206Earlier quoted context omitted.
There's some data here that can help give a clue: https://survey.stackoverflow.co/2022/#most-popular-technolog... . It does look like vscode is the most used by a very large margin.
Scrolling up, the same sample put NPM use at 65.17%, so I feel pretty comfortable calling it sample bias.
Re: Neovim 0.8 Released
#207Earlier quoted context omitted.
Your terminal application is an emulator of a decades old technology originally used in physical consoles, with layers upon layers of enhancements that add support for colors, cursor control, etc. At it's core, it's just a grid of characters. The GUI as a platform is quite literally a superset of the terminal, for example because the terminal emulator app is a GUI itself. Hacking the grid of characters to render line…
The new generation of terminals are nothing like what you’re describing: GPU acceleration, full color support, font shaping, support for ligatures, built-in support for multiplexing, SSH and more. WezTerm [1] is probably the best example right now but there are others. These aren’t your father’s terminals. [1]: https://wezfurlong.org/wezterm/
The "lines" and other UI elements you see in those next generation terminals when you run TUI apps like neovim are still simple characters aligned next to each other to look like a line etc.
Stuff like GPU acceleration is only another layer which was put on top of all of that. At the core they're still using the same old technology.
Re: Neovim 0.8 Released
#208If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ , or new native GUI editors like https://zed.dev/ ? It's impressive to see what the Neovim community has built — preconfigured setups like https://nvchad.com/ are especially wild. But it still feels like a huge amount of work, hoop jumping, and _fragility_ just to reach parity with V…
Re: Neovim 0.8 Released
#209If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors like https://helix-editor.com/ , or new native GUI editors like https://zed.dev/ ? It's impressive to see what the Neovim community has built — preconfigured setups like https://nvchad.com/ are especially wild. But it still feels like a huge amount of work, hoop jumping, and _fragility_ just to reach parity with V…
Re: Neovim 0.8 Released
#210Earlier quoted context omitted.
Yeah it's a tough one. I've switched back and forth relatively freely over the years, but now that new VimScript (vim9 script) has breaking changes and neovim will not be supporting it, it's probably time to pick a pony. I may end up sticking with og vim but my heart has always been with neovim. regular vim would undoubtedly still be stuck in the stone age (including with no :terminal) had neovim not started some com…
Vim has had :terminal since version 8.1 [1]. [1]: https://gist.github.com/mahemoff/8967b5de067cffc67cec174cb3a...
Without neovim, we'd still be on vim 7.xxxxx