[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Tabs are ready? -> Let us give a definition of tabs.

From: martin rudalics
Subject: Re: Tabs are ready? -> Let us give a definition of tabs.
Date: Mon, 06 Feb 2012 11:35:27 +0100

>>> There is the conception of mozilla and many text editors that changing a
>>> tab means to pass to other web page or other file to edit.
>> What does "changing a tab" mean?  Do you mean pushing some graphical
>> object with the mouse or replacing one graphical object with another?
> Yes. Not necessarily with the mouse. You can call a lisp function to
> commute to a new tab. In firefox you can commute to the next tab using
> C-PgDn .

IIUC in firefox you have something like a "currently active tab" which
is higlighted and confers to the page currently shown in the firefox
frame.  In Emacs we can do something similar for tabs conferring to the
buffer currently shown in a window or the selected window.  Highlighting
the tab conferring to "save the current window configuration" doesn't
make much sense to me.  So if the last tab action we activated was such
a save we probably shouldn't highlight the associated tab.  But then
moving ("commuting") to the next tab will happen without visual feedback
from where we started moving.  Think of doing C-PgDn and the next tab is
a "restore window configuration" tab.

> Every time when you commute to a tab, the lisp function associated to the
> 'show event is called.

In firefox moving to the next tab means showing the associated page.
What is the 'show event for "restore window configuration"?

> In mozilla you can install lots of kind of bars. And there is no doubt that
> the tabs are still useful. In mozilla the tabs are used for current-open
> pages.

And that's well-defined IMHO.  Doing something different might be


reply via email to

[Prev in Thread] Current Thread [Next in Thread]