How to get started with Neovim in 2023

[@Linuxdirk]

2:56 DO CREATE your own config from scratch the first time! First because only then you really know what's happening, and second: you might prefer your minimal config afterwards. And if not;: you can still switch to a preconfigured setup.

[@MoreChannelNoise]

Totally agree, trying to figure out how a complicated setup is put together is harder.

[@gerardomahony2268]

I agree with your comment around pre built neovim configs. When delving into the vim/neovim world i had read many comments saying you shouldn't use these and are better off learning by starting with vanilla neovim. I did this and have also used nvchad, astrovim, spacevim etc. finally settling on Lazyvim. While it was beneficial to start from scratch it was also much more efficient to start with a pre config and build it out with a few extra plugins specific to my workflow. I even made my own sumple plugin for running tests in a container. I guess ultimately i am lazy and don't want to spend lots of time configuring to get going hence the Lazyvim config is a perfect match and aptly named 😁

[@alwayshappy2862]

Hey buddy am new in vim field and confused between nvchad vs lazyvinm What you suggest for beginners ?

[@lian1238]

I’m addicted to the PAIN to the point of resorting to installing linux on a VM on my main windows PC just to get the “native” experience.

[@shawnmatyasovszky7994]

I actually am interested in the debugging bit. It seems like a pretty consistent pain point for neovim. I'll usually drop into VS if I need a debugger.

[@ifcodingwerenatural]

If there's one reason why I ever open vscode, it's to use the debugger. nvim-dap isn't too hard to get working, but the debugging experience is still pretty rough imo.

[@brendannolan2508]

It can bed hard-ish to get your debug adapters working but I think the main reason debugging is rough in neovim is this: Debugging requires you to rapidly and repeatedly change panes (going from your code to your stack trace or watchpoints) and jump around buffers (inspecting the values of your variables). You have to do this way more often and way faster while debugging than during normal development and this is where a very un-vim-like mouse comes in handy (hello vscode😅). I'd really like to hear from anyone who has been able to use mouse hover to inspect variable values while debugging in neovim.

[@cariyaputta]

I think if you have some programming knowledge you can start setup your Neovim config from scratch. All it takes is a package manager (I prefer lazy), a couple of core plugins like Mason, Mason LSP, Mason DAP, Lualine, etc. And you're good to go. I like the minimalist approach.

[@MoreChannelNoise]

I agree and I have zero programming knowledge. I find installing and changing things myself easier to understand. If I install a complicated setup like lazy vim I have no idea how it's put together and how to change things

[@niflheims]

Wezterm user too 🙂 But classic Vim user. Never made the leap to nvim. This makes me wanna try it!

[@driden1987]

Hah, to this day, I always ask people for what key combinations they use in search of the most ergonomic keybinding scheme. I'm notably bad at picking hotkeys for my maps

[@ifcodingwerenatural]

Good point, I struggle to add new keybinds because I don't know where to put them anymore, but picking the right keybindings is a different problem than fundamentally understanding how to create them in the first place.

[@driden1987]

@@ifcodingwerenatural Yeah totally, thought it was a fun remark to make!

[@audiocorps2334]

2:53 Ah, yes, because the best starting selection for someone starting out is choosing the terminal emulator with non-existent cross-platform support.

[@h3l_l]

ur cool

[@fathulfahmy]

im interested in your dotfiles. do you mind sharing it?

[@ifcodingwerenatural]

It's been requested enough that I'm considering making it public.

[@fathulfahmy]

@@ifcodingwerenatural Looking forward to it then!

[@karesztrk]

Whats so attractive in Wezterm lately?

[@ifcodingwerenatural]

I've been using Wezterm for years now, it's an excellent terminal.

[@WarloardInPcGamer]

I love wezterm because it provides consistent user experience across all os. As a primary windows user, this is a big selling point for me since most terminal don't focus on windows. And it's config is based on Lua which I really like.

[@naranyala_dev]

tmux, tmux, tmux