@publicvoit mostly, just relearning everything. I was so used to #neovim and its workflow that I was scared to try anything else. I still keep #helix around for very lightweight text editing though.
There's so much content covering tips, tricks, tutorials, plugins, hacks, and anything else I could think about for #Neovim that I could stay busy just playing with my editor even if I never write another line of code.
#Neovim
Use :help index to see default key mappings.
Use :map with no arguments to list all key mappings set by you or a plugin.
A tutorial I followed had me remap <C-T> and of course I did it without even thinking. Then I was trying to navigate :help and I thought something was broken.
Posted a while back about wanting to give #emacs a go for a bit, see what the fuss is about (I'm mostly a #neovim guy).
I've been doing that, specifically with #doomemacs (vanilla was awful, tbh, but Doom has a lot of decent plugins including lsp and Vim emulation out of the box, which makes it very comfortable), and I think I get it now. I'm especially a fan of #orgmode and #orgroam.
For now, I think I'll be using both Doom Emacs and Neovim depending on how I feel. Is...is that allowed?
TIL:
Warum wird der Cursor in vi mit h j k l bewegt?
Warum springt ^ in vi an den Anfang der Zeile?
Warum steht ^ in regulären Ausdrücken für den Zeilenanfang?
Warum steht ~ in Unix für das home-Verzeichnis?
Das alles ergibt sofort Sinn mit Blick auf das Keyboard-Layout des ADM-3A Terminals von 1976.
Challenging myself to use #neovim today instead of #VSCode.
I used to use #gvim about 18 years ago for PHP dev work, but I was never a power user.
I just feel like Code is such a massive app for the sort of coding that I do.
I am very far away from being productive, and I have no idea how to interface with language servers, etc. But I remember how to save and quit, so that's a start.
#NeoVim continues to be a learning experience for me. I followed a guide to get where I'm at, but I'm not sure it was the right guide. I keep seeing a lot of good content referencing different plugins.
My current significant plugins:
lazy.nvim
but a lot of info seems to reference Packer or vim-plug or pathogen or dein or Vundle or don't bother because plugin management is now built-in 😓
nvim-tree
but a lot of info seems to reference NERDTree.
nvim-treesitter
but a lot of info seems to reference fzf (FuzzyFinder)
nvim-lualine
but a lot of info seems to reference vim-airline
mason + mason-lspconfig + nvim-lspconfig
but a lot of info seems to reference coc (Conquer of Command)
@VinceAggrippino I’ve been working on switching from vim to #neovim as well. Had coc setup for vim and working out the details of mason, etc.
Using lazy.nvim and it’s been working well for me.
Using lualine, also working well. Treesitter tools over from NERDTree.
Today I switched from fzf to telescope. It looks like it will be a good solution from the brief experimenting I’ve done to date. Less configuration to get a similar setup.
so been slowly changing up my neovim set up to use LazyVim and ran into some trouble switching from galaxyline to lualine with the theme i spent a lot of time on. buuuuut i just changed it a bit and now i'm really happy with it!
1️⃣ Introduce a few default linters
2️⃣ Add a few LazyVim plugin linters and formatters
3️⃣ Navigate diagnostics across a project
4️⃣ Show how to fix problems
5️⃣ Add your own custom linters