From: Miles Bader <miles@gnu.org>
Subject: Re: Jumping to C source from *Help*
Date: Tue, 20 Apr 2004 19:48:16 -0400 [thread overview]
Message-ID: <20040420234816.GA9689@fencepost> (raw)
In-Reply-To: <f9n056dy1x.fsf@xpc14.ast.cam.ac.uk>
On Wed, Apr 21, 2004 at 12:33:46AM +0100, Glenn Morris wrote:
> > When people use a special-purpose frame like this, they would not
> > mind if C-x b switches to a window in another frame.
>
> Speaking for myself, I'd actively want that behaviour, rather than
> just "not mind". When I set up such a special frame, I want Emacs to
> leave it alone, and to use another frame for Help buffers and such.
> I'm happy for it to pop-up another frame if it needs to, rather than
> messing with the existing one.
Are such users generally considered `expert'? If so maybe it would make
sense to have a `blah-blah-function' variable, which switch-to-buffer would
call in this situation (presumably signaling an error if it's nil).
Then people who have such special environments could make it work exactly
like they wish (some possibilities that come mind are `pop-to-buffer' and
`switch-to-buffer-other-frame').
-Miles
--
((lambda (x) (list x x)) (lambda (x) (list x x)))
next prev parent reply other threads:[~2004-04-20 23:48 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 22:35 Jumping to C source from *Help* Stefan Monnier
2004-04-07 1:01 ` Juanma Barranquero
2004-04-07 19:44 ` Stefan Monnier
2004-04-08 0:35 ` Kim F. Storm
2004-04-08 6:12 ` Juri Linkov
2004-04-08 16:10 ` Kim F. Storm
2004-04-09 22:44 ` Richard Stallman
2004-04-08 16:46 ` Stefan Monnier
2004-04-08 17:27 ` switch-buffer to use other window if dedicated window (was: Jumping to C source from *Help*) Drew Adams
2004-04-09 22:44 ` Jumping to C source from *Help* Richard Stallman
2004-04-10 18:51 ` Kim F. Storm
2004-04-11 23:17 ` Stefan Monnier
2004-04-12 17:34 ` Glenn Morris
2004-04-14 18:01 ` Richard Stallman
2004-04-15 17:36 ` Glenn Morris
2004-04-19 18:20 ` Richard Stallman
2004-04-19 23:59 ` Kim F. Storm
2004-04-20 0:41 ` Glenn Morris
2004-04-20 16:05 ` Drew Adams
2004-04-20 20:47 ` Richard Stallman
2004-04-20 23:33 ` Glenn Morris
2004-04-20 23:48 ` Miles Bader [this message]
2004-04-20 22:04 ` Nick Roberts
2004-04-20 23:40 ` Glenn Morris
2004-04-21 10:21 ` Kim F. Storm
2004-04-21 15:38 ` Stefan Monnier
2004-04-13 17:44 ` Richard Stallman
2004-04-13 18:12 ` Stefan Monnier
2004-04-14 22:53 ` Richard Stallman
2004-04-15 13:58 ` Stefan Monnier
2004-04-15 16:27 ` Kim F. Storm
2004-04-15 16:08 ` Drew Adams
2004-04-16 18:08 ` Richard Stallman
2004-04-16 18:37 ` David Kastrup
2004-04-16 18:08 ` Richard Stallman
2004-04-16 18:39 ` Stefan Monnier
2004-04-17 19:46 ` Richard Stallman
2004-04-19 14:09 ` Stefan Monnier
2004-04-18 21:47 ` Richard Stallman
2004-04-19 14:12 ` Stefan Monnier
2004-04-08 6:19 ` Juri Linkov
2004-04-08 16:07 ` Kim F. Storm
2004-04-09 22:43 ` Richard Stallman
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=20040420234816.GA9689@fencepost \
--to=miles@gnu.org \
/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).