5 ms·
Regarding tabs: I bound F2 to previous tab, F3 to next tab and F4 to new tab. Besides highlighting the current line, I think this is my most important customisa
by archi42 8y ago
Regarding tabs: I bound F2 to previous tab, F3 to next tab and F4 to new tab.
Besides highlighting the current line, I think this is my most important customisation.
- omn1 8y agoOh that's cool! Think I might do that, too. Thanks.
- pault 8y agoIsn't `gt` and `gT` faster? You don't have to move your hands!
- roylez 8y agoIt isn't. I use F11/F12 for previous/next tab, in tmux and browser, and I can confirm it.
- JoshMnem 8y agoI like `gt` and `gT`, because they are available out of the box on remote servers too.
- Lio 8y agoAlso you can use <num>gt to jumpe to, say, second tab.
- geowwy 8y ago`gt` will still be slow because you're using the same finger for both keys.
- ropeadopepope 8y agoI went a slightly different direction. CTRL+N is next buffer (ie: tab), CTRL+P prev buffer, LEADER+W for close buffer. I don't make new buffers a lot, so I just type out :new when I need to. Opening an existing file is LEADER+F, which opens fzy via vim-picker. I reserve the F keys for toggles. F2 is set to pastetoggle. F3 turns numbers on and off. F4 turns special characters on and off.
- teilo 8y agoSince I rarely do window splits, I finally gave up on tabs and just stick with buffers. Tabs in vim aren't really tabs anyway. They are window layouts. If one tries to treat them like tabs, things can get confusing fast. Using Airline, you can show your buffers in a line at the top of the screen and treat them like tabs, which is nice. I map <leader>h and <leader>l to move between buffers.