Could anyone explain to me what is the relationship tabs have with
buffers. The documentation suggests that there could be many windows
within a tab. So, is it a way of having a hierarchy of windows?
I do a ":bufdo tabnew" and vim locks itself up, hogging all system
resources. Is this a feature?
In general, why would one want to use tabs when there was "mini buf
explorer" plugin by Bindu Wavell et al.? It appears that they offer
comparable features -- am I mistaken?
thank you for listening,
- Anand
No, you're not mistaken. I think VIM's creator, Bram Molenaar, said in
the video of his presentation at Google that he does not use tabs. So,
I don't think you are alone in failing to see their utility. I don't
use them because once I take the trouble to open, say, three tabs,
somewhere along the line they seem to spontaneously consolidate back
into one. Or I open another window in one of them and lose my way.
It's easier just to keep track of buffers in my opinion.
I'm sure others will jump in to disagree.
bs
I've noticed the same thing with tabs; it's hard to keep the tab
contents same. However, I occasionally do
:tab :h <some_help_topic>
I find it useful to have the help in a separate tab since I often
unintendedly close it.
tk
I use tabs for keep multi windows settings untouchable. I've tab with
his own name with call stack imitation inside it. When I want to edit
some window I press "to" ( tab open :tabedit % ) and edit it in full
screen mode. after it became not useful I press "tc" ( tab
close :tabclose ). All windows! and positions inside them stay as they
were.
When you close a help window, it is not removed, just unloaded and
becomes a "hidden" buffer.
- Anand
> I've tab with
> his own name with call stack imitation inside it.
What does the this mean and how do you do it? I like the sounds of it,
especially if you mean you can open a tab full screen and then shut it
without disturbing your main window.
Please explain.
Thanks,
bs