Curious about how many Vim/Neovim plugins you’re rocking? 🤔 Jump into your terminal, navigate to your Vim or Neovim configuration directory, and run this command: ls -alp | wc -l. I currently have 41 plugins, but I’m aiming to slim down to 30-35. How about you? Share your plugin count below! #Vim#Neovim#Plugins”
I'm about to update my book on #vim but as I am now mostly using #neovim, I'm a little bit outdated about #vim plugin management. What would you recommend instead of pathogen (for vim, not for neovim)?
People often talk about Emacs vs Vim. Every developer I’ve met uses Vim. Occasionally, some of the vim users will say they have previously emacs, but switched to vim.
So where are all the people who are currently using Emacs?
I’m not trolling or looking for an argument. I legit want to know!
A while ago I made a video showing my 80/20, including Vim's leader key, FZF, jedi-vim, more undo history, disallowing saving upon syntax errors, and more. 💪
👾 This presentation covers #Vim 101 to provide an understanding of how Vim works. Want to know why we use :q to quit Vim? You'll learn that and more in this talk. https://www.youtube.com/watch?v=zxdQJlB65lA
"I hope you don’t mind me asking but what keeps you coming back to #Emacs? I am currently wondering whether to look at #Neovim again - it does seem to be faster and with a strong community around it."
I've been dinking around with #vim a bit lately. Looked some of the help info and I have a serious question: why are some of the keyboard shortcuts so arbitrary?
Ctrl+] to follow a link but Ctrl-T to go back? I can't see the logic. Is there any to this?
Daily driver is now a #OptiPlex 7060 Micro. 😉
In the end all I need is #Firefox and a good editor like #Vim - and of course my trusty #Debian :debian:
This system has also a NVMe inside which can be used for another OS of choice.. more on that later 😎
If I want to do some gaming I can fire up the #Ryzen system - but that is quite rare already.
So, saving energy and getting work done is a good deal 🙂
@nixCraft I've been using #vim for 20 years (now using #neovim ). It's still lean and mean when used "vanilla". However, if I enable the autocomplete, autocompile, auto spellcheck, treesitter, folding, etc. then it noticeably takes up CPU as I type. I don't mind paying some CPU for this...
But for eyecandy I really couldn't care less. Loved my keyboard only #fvwm setup. When I switched to #wayland I finally gave up fvwm for #kde . Happily, kde is lean and fast even with eye candy...
Vim Lands XDG Base Directory Specification Support | Phoronix
「 Rather than just dumping all configuration files / cache / data into the home directory folder, Vim can now respect the XDG Base Directory specification with regards to the directories such as for the XDG cache, configuration files, persistent data files, and state data files 」
PSA: If you're using Ruby LSP on neovim with nvim-lspconfig, I just renamed the config name from ruby_ls to ruby_lsp, and you might see a warning like this:
ruby_ls is deprecated, use ruby_lsp instead.
This feature will be removed in lspconfig version 0.2.0
The LSP will continue to work, but if your LSP setup doesn't use something like mason, you should be able to replace ruby_ls with ruby_lsp to avoid this warning.