>0 sika @ 2025/07/09 20:29
I usually use Neovim (nvim) for text editing tasks. By default, it feels a bit brutal but you can easily install full setup like https://www.lazyvim.org/. To master quickly the tool, I recommend https://github.com/m4xshen/hardtime.nvim. And you ? Do you have any practical recommendations for nvim ? Do you use it everyday ?
>1 mai @ 2025/07/10 02:30
>>OP The charm of (Neo)vim to me is being able to customise it as much as possible to be comfortable for myself, so I personally never touched any of those Neovim distros, just kickstart.nvim. My recommendation is checking around for useful plugins while also keeping in mind that the more plugins you use, the more complexity you add, so it can get a bit chaotic.
>2 sika @ 2025/07/10 06:48
>>1 I agree for the complexity but it can be softened with tools like https://github.com/folke/which-key.nvim which show available keymaps when you type. And Lazygit only loads plugins that you need according to the filetype.
>3 werdl @ 2025/07/17 17:40
On less powerful computers, heavy configs can be an issue. I agree with avoiding complexity. If you want a fully-featured IDE, just use VSC with Vim Mode or similar.>>2
>4 dotuncle @ 2025/07/19 21:15
i saw this article about a very simple neovim config: https://yobibyte.github.io/vim.html very interesting. it uses no plugins. i'm not ready to go that far yet but they make an interesting case about distractions.
>5 ant @ 2025/08/04 22:00
>>OP One simple yet important adjustmet is to use a more reachable key for exiting to command mode, because vi was made back when thekey was roughly where the modern or key is. If vi (for I am using the real vi) allowed it, I should use for , but I can't seem to entere that mapping in vi, and have decided to go along with the standard recommendation -- jk.
>6 jazei @ 2025/10/07 22:06
I use Vim and for me most important is kill the capsLock key. Vim gets crazy when I (by error) press that Fuck... key. I use an alias in my shell for kill it alias dM='setxkbmap -option caps:escape' and another alias for get capslock alive again about plugins: here we can not get they: we haven't any hardtime or MRU or etc Thank you and Regards! >>OP
>7 anonymous @ 2025/10/08 13:07
>>OP I ran down the scale, I guess. When I really got into vim, I read a lot of other people's .vimrc's and copied what looked good. But I eventually started pruning out the things I didn't use and my .vimrc kept shrinking. When it was down to just a few lines, I said to heck with it and went to: alias vim='vim --clean -i NONE' But then again, I don't do a lot of coding (and when I do, I use ed.)
>8 ant @ 2025/10/11 19:34
>>7 Is not coding in a line-oriended editor painful?
>9 anonymous @ 2025/10/16 00:10
>>8 ~ant It's not painful if you mostly code only short scripts.