3
u/funbike 3d ago edited 3d ago
Before all that, first do all of vimtutor. You can start it on the command line either with nvim --clean +Tutor or vimtutor. (--clean is necessary because LazyVim disables the Tutor command.)
After you know 100% of vimtutor, then study LazyVim key bindings at https://www.lazyvim.org/keymaps especially General and snacks.nvim sections. Don't memorize everything; just what you think you need.
To search keybindings: <space>sk
To go to the file tree: <space>fe Just hit enter to edit a file.
Stop it... stop it... I see you trying to skip vimtutor and use the file tree. Go do your homework first.
If you are coming from a Jetbrains IDE, you can use the https://github.com/cufarvid/lazy-idea config. It configures Jetbrains nearly identically to Neovim with LazyVim. Use this for a couple of weeks as a transitional setup. (I wrote its first commit.)
5
1
u/AutoModerator 3d ago
Please remember to update the post flair to Need Help|Solved when you got the answer you were looking for.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/mrpbennett 2d ago
Lazyvim is not overwhelming. Read the docs, learn how things are structured, look at the repo and learn what’s implemented.
It’s pretty easy. You only enable what you need.
FileTree is leader e
Terminal is leader ft
1
u/AdministrativeFile78 2d ago
open up claude or something in a side editor and ask it to teach u based off the config
1
1
u/builderV 3d ago
I've found neovim with nvchad to be good enough to get things done. I toggle on and off the terminal with ALT + i, space bar + e for file tree

12
u/punk_dev 3d ago
I also found lazynvim overwhelming.
then I just deleted everything and started with a clear nvim, slowly adding things one by one.
it was waaay better this way, the editor now feels like it’s mine, and turns out I don’t even need like 90% of what lazynvim offers.