I'm playing around with #LazyVim and a clean config. Not sure if this is a LazyVim question, or a #Vim question, or an #nvim question, but what are the keyboard shortcuts for these autocomplete dropdowns? Is this "omni" completion?
<c-n> for next item, <c-p> for previous, enter to accept the suggestion? Is there anything else? I'm not sure where to find these in the help
@RL_Dane
You could close some web browser with vim commands and key bindings. There's a couple of web browser that use vim keys by default, the first one that comes to mind is Qutebrowser, but there's others too. In this way you can avoid the disappointment and being confused why my keybindings doesn't work⁉️ 😅😜
I want a reality TV show where a hardcore linux nerd and someone who knows absolutely nothing about technology trade their setups for a week. The Linux nerd gets one hour to explain their setup to the tech noob, then they're both on their own. The noob would have to wrap their heads around the alien Hyprland and Neovim bindings and figure out how to get things done without unfree software, and the linux nerd would spend most of their time complaining about the design decisions of Apple/Microsoft/Google and being paranoid that the unfree software is CIA spyware. No matter what, it would be quite entertaining.
Wenn ich Ctrl+o drücke, werden zuvor geöffnete Dateien in einen neuen Buffer geladen. Ich finde die Tastenbombination aber weder in :map noch in der Dokumentation von NeoVim oder LazyVim.
There's always something new for me to learn in #Vim. Today, it's even more registers, and how to insert them into weird places (like inserting the current filename into a command using <C-r> %) https://www.brianstorti.com/vim-registers/
@annika there’s a great plugin for #nvim, which-key, that helps expose registers and key bindings. Maybe there’s something similar for #vim? I recently started using it in my config and it’s been awesome. FYI, you can directly use % register in a command and it will get interpreted. <c-r> not needed in that context.
@b0rk ooh I like the look of delta. Thanks for sharing!
I use lazy git, mostly for commits, it has some useful features like Amend, reword commit. I sometimes rebase in lg too, jumping out to #neovim with 'e' if it gets tricky.
Ripgrep is the faster new 'ag' that I've not made the jump to (used to silversearcher-ag's arguments). But a lot of these tools are built-in to #nvim with plugins lilke #telescope
I also have a simple alias git-show-tree for got log that I can't do without.
I see a great number of people picking packaged distributions like #AstroVim, #NVimChad, #LazyVim or simply moving to other editors like #Helix or #Kakoune because the configuration and/or the ecosystem became a burden to manage.
Maybe, they have too many plugins and missed the power of the close-to-vanilla editor?
I've a dozen hand-picked plugins and have been fine for years.
Agreed it's not shinny, but it works damn well and never breaks.
This is the first Neovim release since Bram Moolenaar passed away and the archival/deprecation of both null-ls.nvim and packer.nvim.
Is anyone running into any issues with this release (particularly if you use null-ls or packer)? How are the Neovim distros (eg - NvChad, AstroNvim, LazyVim, LunarVim, etc.) performing after the update?