From: Juri Linkov <juri@jurta.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: how about a find-library-other-window command?
Date: Wed, 20 Jun 2007 00:54:35 +0300 [thread overview]
Message-ID: <87bqfb7grk.fsf@jurta.org> (raw)
In-Reply-To: <jwvhcp3n0m1.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue\, 19 Jun 2007 16\:41\:36 -0400")
> - make <foo> use a new command like `switch-or-pop-to-buffer' which behavior
> depends on a "config var".
Maybe some more clear and short name like `show-buffer'.
> - add prefix keys such as C-x 4 which can force one of the two behaviors for
> the next command (or maybe just one prefix key C-x 4 which toggles the
> behavior of the next command).
C-x 4 or some such prefix could automatically add the command's context
(buffer name + this-command) to the config variable, so the next call
without C-x 4 will reuse this preference once explicitly defined by calling
the command with the C-x 4 prefix.
> - make the "config var" sufficiently complex that it doesn't just choose
> "always pop" or "always switch" but can choose different defaults for
> different commands. How to do that is up-in-the-air:
> - Maybe switch-or-pop-to-buffer would look at this-command (yuck) and do as
> assq search in a config alist based on that.
> - Or switch-or-pop-to-buffer would take an additional argument to specify
> the key to use an the alist search.
> - It would probably be good to be able to specify not just different
> behaviors depending on the command but also depending on the buffer in
> which it is executed (e.g. "always use switch when done inside a *Help*
> buffer").
If there are too many parameter types used in the config variable (the
target buffer name, the source buffer name, this-command), another option
would be to allow a predicate function in such a config variable.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2007-06-19 21:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 18:23 how about a find-library-other-window command? Drew Adams
2007-06-19 19:08 ` David House
2007-06-19 19:39 ` Sean O'Rourke
2007-06-19 19:52 ` Drew Adams
2007-06-19 19:51 ` Drew Adams
2007-06-19 21:40 ` David Kastrup
2007-06-20 1:03 ` Stefan Monnier
2007-06-20 13:28 ` Richard Stallman
2007-06-19 19:15 ` Stefan Monnier
2007-06-19 19:36 ` Drew Adams
2007-06-19 19:53 ` Andreas Schwab
2007-06-19 20:41 ` Stefan Monnier
2007-06-19 20:55 ` Drew Adams
2007-06-19 21:54 ` Juri Linkov [this message]
2007-06-20 13:28 ` Richard Stallman
2007-06-20 14:09 ` Juri Linkov
2007-06-20 14:57 ` Andreas Schwab
2007-06-20 15:44 ` Juri Linkov
2007-06-21 1:07 ` Richard Stallman
2007-06-21 7:43 ` Juri Linkov
2007-06-21 9:55 ` David House
2007-06-21 9:57 ` David House
2007-06-21 10:49 ` Kim F. Storm
2007-06-21 11:38 ` Andreas Schwab
2007-06-22 1:51 ` Richard Stallman
2007-06-21 10:49 ` Andreas Schwab
2007-06-20 17:21 ` Ehud Karni
2007-06-20 17:54 ` Juri Linkov
2007-06-21 1:07 ` Richard Stallman
2007-06-19 23:24 ` Davis Herring
2007-06-19 23:30 ` Drew Adams
2007-06-20 13:28 ` Richard Stallman
2007-06-20 13:28 ` Richard Stallman
2007-06-20 14:17 ` Juri Linkov
2007-06-20 16:49 ` Drew Adams
2007-06-21 1:07 ` Richard Stallman
2007-06-22 19:29 ` Juri Linkov
2007-06-22 20:40 ` Drew Adams
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=87bqfb7grk.fsf@jurta.org \
--to=juri@jurta.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).