AW: AW: AW: Tabs in Emacs?

["Berndl, Klaus" <klaus.berndl@capgemini-sdm.com>]

Well - "argh" is well spoken ;-) 

Another suggestion, or precisely a refined suggestion:

1. Introducing new commands which represents your scenario where opening a new buffer opens a new tab (e.g. find-file-other-tab, switch-to-buffer-other-tab, adapting display-buffer in an appropriate manner etc...) Optionally we could also introduce some new defcustoms which can define a default-behavior: e.g. using the standard window-related commands (e.g. find-file-other-window) automatically opens/uses other tabs ...

2. But in general tabs represent window-configs and leaving a tab X stores ist window-config in a suitable way so it can be restored when entering again tab X - all this has to be happen automatically! Often the window-config will only contain one window...

So when a user wants the tab=buffer relation, he has it - he just has to use Emacs in way so opening buffers and switching to buffers operates on tabs (see 1) - but the whole stuff is much more powerful for scenarios where a tab contains a full window-config. The latter one is similar to something like escreen.el and winring.el and could be usefol for running in one tab ECB, in another Gnus, in another GUD - like eclipse...

Thoughts?

-----Ursprüngliche Nachricht-----
Von: miles@gnu.org [mailto:miles@gnu.org] 
Gesendet: Mittwoch, 18. November 2009 10:53
An: Berndl, Klaus
Cc: Angelo Graziosi; Emacs; Deniz Dogan
Betreff: Re: AW: AW: Tabs in Emacs?

"Berndl, Klaus" <klaus.berndl@capgemini-sdm.com> writes:
> IMHO tabs should an a frame-basis and each tab should display window-configurations, i.e. switching to a tab X should display exactly the window-layout and contents as X has contained when the user has left it
> And each window of the window-configuration of a tab should contain it's headerline...
>
> Is this understandable?

Sure, but... it may not exactly be what's most convenient for users --
again, it's a hard issue.

While a window-configuration switching implementation is useful in some
cases (e.g. eclipses uses a sort of similar system for switching between
"debugging view" "browsing view" etc), how would the different
configurations get set up ?  I can imagine a system that required
explicit user action ("add a new tab with current config"), but... 

I think many users might just want to switch between buffers, and have
tabs automatically added for each buffer (perhaps limiting the number
displayed in a MRU fashion, e.g., how eclipse handles source file tabs).
That seems to be more similar to how tabs work in e.g. visual studio,
and other editors...

argh... :]

-miles

-- 
Suburbia: where they tear out the trees and then name streets after them.