From: martin rudalics <rudalics@gmx.at>
To: Alin Soare <as1789@gmail.com>
Cc: Juri Linkov <juri@jurta.org>,
Juanma Barranquero <lekktu@gmail.com>,
Emacs Dev <emacs-devel@gnu.org>
Subject: Re: Tabs are ready? -> Let us give a definition of tabs.
Date: Mon, 06 Feb 2012 18:03:36 +0100 [thread overview]
Message-ID: <4F3007E8.6090209@gmx.at> (raw)
In-Reply-To: <CA+Xtq3WfrTBjCi9Yedt7jaTYU_XbbWC7BkeJwMG0=nqY4cFtLA@mail.gmail.com>
>> 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.
>
>
> In order to be able to restore a window configuration you have to save it
> first.
Which has been done as described in the text above.
>>> 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"?
>
>
> Restoring the saved window configuration, for example.
Showing another buffer in a window is reversible. You can easily switch
back to the buffer shown before. Restoring a window configuration is
irreversible unless you save the current configuration when restoring.
Providing such behavior via a "show" event is confusing at least.
martin
next prev parent reply other threads:[~2012-02-06 17:03 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 22:36 Tabs are ready? -> Let us give a definition of tabs Alin Soare
2012-02-05 10:42 ` martin rudalics
2012-02-05 12:44 ` Alin Soare
2012-02-05 13:17 ` martin rudalics
2012-02-05 13:39 ` Alin Soare
[not found] ` <CA+Xtq3U5PkH=m1ZRMMm2LJQ_BHZXc08Vk4TbhNyyFLta+1EkBw@mail.gmail.com>
2012-02-05 13:44 ` Fwd: " Alin Soare
2012-02-05 14:50 ` Alin Soare
2012-02-05 17:56 ` Andy Moreton
2012-02-05 18:51 ` Drew Adams
2012-02-06 3:35 ` Stephen J. Turnbull
2012-02-05 18:16 ` martin rudalics
2012-02-05 21:33 ` Alin Soare
2012-02-06 10:35 ` martin rudalics
2012-02-06 13:21 ` Alin Soare
2012-02-05 23:56 ` Alin Soare
2012-02-06 10:36 ` martin rudalics
2012-02-06 13:34 ` Alin Soare
2012-02-06 14:46 ` Stephen J. Turnbull
2012-02-06 16:18 ` Alin Soare
2012-02-06 16:21 ` Alin Soare
2012-02-06 17:53 ` Stephen J. Turnbull
2012-02-06 22:51 ` Alin Soare
2012-02-06 22:55 ` Alin Soare
2012-02-07 16:15 ` Stephen J. Turnbull
2012-02-09 15:55 ` PJ Weisberg
2012-02-09 16:11 ` Alin Soare
2012-02-09 16:16 ` Alin Soare
2012-02-10 19:04 ` Alin Soare
2012-02-10 19:08 ` Alin Soare
2012-02-11 14:16 ` Nix
2012-02-11 14:41 ` Alin Soare
2012-02-12 13:40 ` Nix
2012-02-12 16:23 ` Alin Soare
2012-02-12 18:48 ` Alin Soare
2012-02-13 6:06 ` Stephen J. Turnbull
2012-02-13 12:29 ` Nix
2012-02-13 15:53 ` Tom Tromey
2012-02-13 16:21 ` Nix
2012-02-13 16:30 ` Tom Tromey
2012-02-13 18:50 ` Nix
2012-02-15 20:35 ` Tom Tromey
2012-02-15 22:59 ` Stefan Monnier
2012-02-15 23:03 ` Nix
2012-02-28 15:13 ` Alin Soare
2012-02-28 15:16 ` Alin Soare
2012-02-13 13:24 ` Stefan Monnier
2012-02-13 13:49 ` Nix
2012-02-13 15:20 ` Stefan Monnier
2012-02-13 16:21 ` Nix
2012-02-06 18:00 ` martin rudalics
2012-02-06 17:05 ` martin rudalics
2012-02-05 18:15 ` martin rudalics
2012-02-05 21:38 ` Alin Soare
2012-02-05 22:30 ` joakim
2012-02-05 22:53 ` Alin Soare
2012-02-06 10:35 ` martin rudalics
2012-02-06 13:25 ` Alin Soare
2012-02-06 17:03 ` martin rudalics [this message]
2012-02-06 19:19 ` Nix
2012-02-06 19:43 ` martin rudalics
2012-02-06 19:45 ` Nix
2012-02-06 19:54 ` Drew Adams
2012-02-08 23:43 ` Alin Soare
2012-02-09 11:19 ` Nix
2012-02-09 13:05 ` Alin Soare
2012-02-09 13:07 ` Alin Soare
2012-02-07 15:57 ` Stephen J. Turnbull
2012-02-07 17:15 ` Nix
2012-02-06 20:05 ` Alin Soare
2012-02-07 16:03 ` Stephen J. Turnbull
2012-02-06 17:04 ` martin rudalics
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F3007E8.6090209@gmx.at \
--to=rudalics@gmx.at \
--cc=as1789@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).