Re: Separate area at the top for a serious tab bar

[R. Diez]

> [...]
> I would highly reccomend giving the buffer
> based workflow a try, however. Once I tried seriously
> dropping tabs, I can't imagine going back to a tabbed workflow.
> [...]

You are not the first with that kind of suggestion.

I still have not seen what makes that "buffer based workflow" better. Sometimes 
I do use ibuffer to clean buffers up, or to find some buffer I 'lost', but tabs 
give you a kind of positional orientation that is hard to beat.

I do not switch buffers with the mouse. I use Ctrl+Up and Ctrl+Down to navigate 
the tab bar. With Ctrl+Shift+Up and Ctrl+Shift+Down I can reorder the tabs with 
the keyboard. I do this all the time, so that the buffers I am working on at 
the moment are near each other.

By the way, those are exactly the keys that Firefox uses for its tabbar.


For example, when working on C/C++ code, I place the .h and .cpp files next to 
each other, the .h file to the left, and the .cpp file to the right. I know I 
can open the other one with 'other', but that is not reliable, for example, if 
the .h file is not next to the .cpp file, but in some other include/ directory. 
If I am moving code, I place the old source file to the left, and the new one 
next to it, to the right, so switching is immediate. I can open a script and 
have next to it a shell to test it out. And many such pairs happily coexist in 
the same, long tabbar.



Best regards,
  rdiez