3 ms·
The Vim configuration is something deeply personal, but I'd recommend as a wise choice always explore first the default settings because assuming those in your
by rgomez 2y ago
The Vim configuration is something deeply personal, but I'd recommend as a wise choice always explore first the default settings because assuming those in your workflow gives an huge advantage using any new unconfigured vim environment eg to get out of any of the edit modes <C-c> works by default and is a great choice.
To use CUA alike shortcuts there's already:
```
source $VIMRUNTIME/mswin.vim
```
And finally, is also a good idea to get used to use <Leader> as a prefix for your own shortcuts, in my case I use the space bar as <Leader>.
- windward 2y agoStrong agree. Failure to grok what comes with Vim often results in a permenent Nerdtree pane.
- kombine 2y agoI've been using Neovim for about 6 months now but as a former VS Code user I was mostly investing into the various plugins. Fairly recently I started digging deeper into vim's built-in features such as vimgrep and quickfix and they are incredibly powerful. It will take me probably another year to learn to use all these tools effectively.
- ttyprintk 2y agoIn its contrib directory, git comes with jump. `git jump grep` will load grep results into quickfix.
- curioussavage 2y agoEh. I tried to buy into this for years but I think my poor working memory just pushes me towards having something like it open. Maybe a little less now that I’ve become a heavy user of tabs. When I start working on a unique task I create a new tab with a few splits with the files I’m interested in. In a way tab views are how I externalize my working memory. But a file tree is still useful to me because file names don’t stick so using a command or picker to swap is often slower
- ulbu 2y agonote that exiting a mode with <c-c> prevents autocmd events from firing. (so I have inoremap <c-c> <esc>)