On 6/15/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Eric Arnold wrote:
When compiled with this patch, Vim will allow the strings delivered
via the 'tabline' option to wrap onto new lines. It is up to the
'tabline' string or function to limit itself. See TabLineSet.vim for
an example of a script which does this.
The default behavior, ie. when 'tabline' is empty, is not changed.
In my opinion the tabline should be one line. When it wraps the UI
looks ugly. Esp. if the currently selected tab page is in the first
I don't understand how the line where the selected tab resides makes a
difference. Is there something I could do to make it better?
line.
It's true that it loses some simplicity. However, when you have lots
of files open (i.e. 15+, when I'm working on several parts of an
application at once), the tabline begins to lose all usefulness,
especially if you are using a custom extended format.
As an example, I use the tabline my TabLineSet.vim to contain buffer
names for all open windows (plus some other stuff), which I've found
very helpful when I have a lot of tabs with multiple windows in them.
I left the default operation alone, so the UI would remain simple
unless forced to wrap by a custom function. Would it help if I added
a special % directive that the custom function could use to enable
wrapping, and have the default for custom functions also remain
unwrapped?
The mechanism to allow an arbitrary number of % items in 'statusline' is
good though.
