4 ms·
This looks very cool, kudos on the launch! I feel like vim tutorials mostly focus on navigating and editing a single file, which is great! But I mostly struggl
by xavdid 4y ago
This looks very cool, kudos on the launch!
I feel like vim tutorials mostly focus on navigating and editing a single file, which is great! But I mostly struggle with how to replicate opening a whole directory in VSCode, which makes it easy to browse the directory, switch between files, open multiple panels, etc.
I'm almost certain vim does all these things out of the box, but tutorials always end at "this is how you edit some text quickly" and never cover "this is how you do software engineering".
- vidyesh 4y agoI am new to using vim too so NerdTree is a little hard for me to use and navigate and the split windows too are difficult to understand in vim. Not many tutorials or guides or courses cover that well. So I have the same issue as you, I really like using neovim for smaller projects as its easy to work on them through the shell. But when it comes to big projects I go back to VSCode with the Vim emulator extension as it just makes using the tree much easier for me in VSCode. I have setup custom keybindings and settings to launch the directory when needed or the command palette works great to launch other files. I wish there was a resource to help switch VSCode to neovim while retaining some of the "most" used VSCode features.
- bootstrappit 4y agoThat's exactly how I feel too. I just started using neovim a few weeks ago. I'm using `nvim .` to get to a navigable tree, but have no idea if that's the right way to do it.
- RMPR 4y agoYou may want to check out Practical Vim by Drew Neil, he covers that aspect.
- xavdid 4y agoGood to know, thank you! I'll check it out.