Vim Doesn't Need Tabs

Подписаться 53 тыс.

Просмотров 11 тыс.

50% 1

If you come from IDEs probably one of the first questions you ask is where are the tabs in Vim.
Though Vim actually has a tabs feature, using buffers and windows instead of tabs is a lot more efficient for most cases and in this video I will show why.
📻 Subscribe for more Vim videos 📻

Опубликовано:

29 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 22

@nirlichtman Год назад

For more Vim tips check out my playlist: ru-vid.com/group/PL0tgH22U2S3GN7MdobsdWV44qw-P5g7RJ

@Gett37 11 месяцев назад

Nice, now I can watch vim tutors on my Siemencs C65 128x128 display

@GoofyTHPS Год назад

wtf is that zoom level, you trynna make vim tutorials for the elderly?

@nirlichtman Год назад

this made me laugh 😂

@tedburke525 11 месяцев назад

I find this zoom level comfortable for watching on phone.

@xrehpicx 10 месяцев назад

Yeah actually very useful on mobile

@EEEEMMMMKKKK 9 месяцев назад

I like it😊

@GiovanniCKC 11 месяцев назад

q is really nice thanks!

@GiovanniCKC 11 месяцев назад

I feel like people rag on tabs too much in vim. In vanilla vim, tabs still feel more efficient to me. - we still can do :bufdo with :tabdo - we can see all our opened files without extra config or running a command - switching between views is faster (gt/T is faster than :bn/N, and just as quick as n and also quick relational movement with [count]gt/T) *And* I don't have to worry about window management because the file takes up my whole screen at all times (personal preference). I still don't entirely get where buffers become more efficient in vanilla vim. The most I have to do to get tabs up and running is map t to :tabnew and now I'm set. Perhaps once I'm using and switching between more files that I might not beable to see..? But even then vim tabs just find a more width-efficient way to display the filepath.... so idk. What am I missing??

@anon_y_mousse 10 месяцев назад

I mapped \t to prompt for the filename because I almost never want to open a blank tab, but if I do I can just hit enter and it's the same thing. I also mapped and to :tabn and :tabp for super fast navigation and set showtabline=2 in my ~/.vimrc because I've got the screen real estate and can afford one more line always used up. I've found that if I need two things open and visible at the same time that it's better to have two terminals side by side so I can just alt-tab between them and it's faster for me. Not that it's exactly tab related, but I mapped \w and \W to turn word wrap on and off which I only need on rare occasions when I use a narrower than half-width window for Vim, like when I've got a window open to write notes while watching a video on RU-vid and it only covers the side panel so I can still see the whole video.

@farzadmf Год назад

I'd personaly argue that tabs are still useful to "group" related buffers

@nirlichtman Год назад

Tabs in Vim indeed can serve the purpose of having different "workspaces" for example Dev and Testing, each with its related windows (as @kjz87 corrected, buffers are invisible and windows are views to a location in a buffer and they are what you put in a tab). It is quite rare (for me at least) to need more than one workspace at the same time for a source code I work on so I barely used the tabs feature. The important point is that tabs are used very differently in Vim as compared to IDEs which use tabs to represent open files, and in most cases you won't need more than a single tab in Vim.

@farzadmf Год назад

@@kjz87 or that 😆