Does anyone know of a nice git interface for Neovim? I would love to get off of emacs, but it's hard to beat Magit. At the very least something that lets me view the repo status and stage selections would be good.
Why quit emacs when evil-mode exists? Fast startup times are solved by never quitting emacs :) Really, emacsclient starts nearly instantly, and all the heavy stuff like language servers and emacs proper just run in server mode. (Disclaimer: I know enough vi and often use it.)
Neovim 0.5 is overpowering
31–40 of 429 posts
Re: Neovim 0.5 is overpowering
#32Earlier quoted context omitted.
1) Terminal 2) Neovide : https://github.com/Kethku/neovide 3) Neovim-Qt : https://github.com/equalsraf/neovim-qt
Your comment triggers my OCD in 2-3 different ways: 1. First you start numbering with 1. 2. Then you start numbering with 0. 3. You provide links for all but the first element in the list, which, combined with my first 2 points, results in a juxtaposition of "2" and "0", suggesting to my subconscious that I missed something. Well done.
Re: Neovim 0.5 is overpowering
#33Does Neovim support webviews in extensions? Can it?
There are a lot of useful visualization tools that VS Code allows that require them. It's one of the most powerful features of the editor, imo.
Re: Neovim 0.5 is overpowering
#34I use nvim in the terminal and gvim/macvim on the desktop. I don't like how the nvim community seems to be throwing themselves wholeheartedly into lua and lua-only plugins (vimscript plugins are better because they work with both vim and neovim). Switching to init.lua also means losing all compatibility with vim, and I cannot fathom why people would want to do that considering that there is nothing that init.vim cann…
I think you mean "vimscript plugins are better for plugin adoption because they work with both vim and neovim".
From the language-design, performance, documentation, robustness/general codebase quality, and total number of users perspectives, Lua is overwhelmingly better than vimscript.
> I cannot fathom why people would want to do that considering that there is nothing that init.vim cannot already do
Ahh, yes, the Turing-equivalence fallacy: "technology A is theoretically capable of doing everything that B does, therefore they're equivalent". Brainfuck and Python are Turing-equivalent, and yet nobody would seriously argue that they're interchangeable.
Design matters.
Re: Neovim 0.5 is overpowering
#35I switched from vim to neovim because I thought I needed to to use coc.nvim - turns out I didn't need to, coc.nvim works in vim 8+ As a neovim user who is just having neovim load my vimrc - nothing neovim specific -, I don't see a huge difference. Are there features I am missing out on? I do like the idea of having everything in my vimrc so I could still use it with vim on a server if needed.
Re: Neovim 0.5 is overpowering
#36Re: Neovim 0.5 is overpowering
#37Vim's editing language feels most powerful when I'm using its text objects: "ciw" means "change in word", "cis" means "change in sentence", and so on. But Vim's built-in text objects are not always a perfect match for the code you're editing. Suppose you want to change the first argument of a function, for example; there's no built-in "first-argument" text object. But Treesitter integration makes it easy to create text objects that understand the AST. Without much effort, users will be able to make mappings like `cia1` to "change in argument 1", and these mappings will work across all languages with Treesitter support.
Re: Neovim 0.5 is overpowering
#38I have an honest question, the real advantage of Vi is its installed everywhere, and just works over ssh. What is the benefit of a terminal IDE like neovim or vim with tens of something plugins? Vscode or other powerful IDEs do the work much better.
Re: Neovim 0.5 is overpowering
#39I have an honest question, the real advantage of Vi is its installed everywhere, and just works over ssh. What is the benefit of a terminal IDE like neovim or vim with tens of something plugins? Vscode or other powerful IDEs do the work much better.
You can speak that language in Vscode... kiiiiind of, just like you can speak evil to emacs. But these are dialects, vim is the real deal.
Neovim with a ton of plugins offers a lot of what an IDE brings to the table, and lets your fingers speak fluent vim at the same time.
So when you're randomly shelled in to some stock install that's got vi (realistically this is mostly vim but it doesn't have to be) you can keep speaking your native language for whatever text editing you might happen to do.
Re: Neovim 0.5 is overpowering
#40Neovim 0.5 is awesome. It has native LSP support, Lua configuration support that it feels like true revolution over past versions. But, getting into optimal setup in neovim/vim involves lot of configuration. Here is mine if you want to refer: https://github.com/varbhat/dotfiles/tree/main/dot_config/nvi...
I tried out the native LSP support few months ago and the docs + features for it seemed poor. I went back to coc.vim
With that said, you can build things quite nicely with it. For example, I have a custom linter setup, custom loclist/quickfix list formatting and populating from LSP data, and a bunch of other things; all using the foundational work coming in NeoVim 0.5.
If anybody is curious, you can find my NeoVim configuration here: https://gitlab.com/yorickpeterse/dotfiles/-/tree/master/dotf...
p.s. In case anybody wonders "why Lua?", for me this mostly comes down to this: I hate Lua, but I hate Vimscript even more.