Tony Mechelynck wrote:

> On 15/09/09 19:38, Patrick Gen-Paul wrote:

>> I have to count the tabs so as to be able to issue {count}gt's or else
>> issue a ":tabs" 
> 
> see :help tabpagenr()

Sorry for being unclear - I have for instance ten tabs and I see in the 
tabline that I have my .vimrc in one of them and would like to go there 
directly. At a glance it could be tab #3 or tab #4. Without the tab 
number displayed, I need to count the tabs, 1, 2, 3, etc. to determine 
which tab I want to go to - or else use the ":tabs" command.

Having the tab number displayed makes navigation between tabs a lot easier.

[..]

> click X (with the mouse) to close the current tab IIRC.

Doesn't do anything. :-(

[..]

>> I'm curious as to why the tab line was implemented this way rather than
>> something like the status line. I'm not complaining, mind you, writing a
>> simple function was definitely a fun and useful experience - vim is an
>> editor for programmers, not a word processor, right ;-) - but I'm not
>> sure why it was not done the same way for the terminal as for the gui -
>> cf. :h set guitablabel..?
> 
> it _was_ done like the status line i.e. for the whole width. You can 
> display what you want in it, even just the number of the current tab...

With gvim, something like ":set guitablabel=%N\ %f" defines a template 
for your labels and vim automatically takes care of building each actual 
label.

Unless I missed something, the equivalent option is not available for 
users of non-gui vim.

What I meant initially was that whereas with gvim, basic tab line 
customization is provided in a way that's similar to the status line, 
with non-gui vim, you cannot define a template, and customizing your tab 
line requires that you write code that will create it dynamically.

Could this be because the tab line was first felt to be something that 
would fit in nicely with the gui model, and only implemented in terminal 
vim as an afterthought?

[..]

> If you send it as attachment SeaMonkey doesn't necessarily know 
> the file's encoding..

My bad - just discovered how I can change the character encoding after I 
start composing my reply.

[..]

Thanks,

Gen-Paul.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Reply via email to