From: Miles Bader <miles@lsi.nec.co.jp>
Cc: tzz@lifelogs.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: next-error-last-buffer
Date: 13 May 2004 16:28:16 +0900 [thread overview]
Message-ID: <buo3c643hwv.fsf@mctpc71.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <87fza4x53v.fsf@mail.jurta.org>
Juri Linkov <juri@jurta.org> writes:
> But there is the variable `display-buffer-reuse-frames' for users who
> like to reuse windows on another frames.
That is too general: it affects _all_ use of display-buffer, including,
crucially, `pop-to-buffer'. In that context, the effect is not just
annoying, it's downright dangerous (as the user expects the keyboard
focus to be the new popped-to buffer -- and it _looks_ like it is
because the window is raised -- but in fact, the frame focus doesn't
change).
So setting `display-buffer-reuse-frames' to t is not reasonable.
> I even have no objections to changing its default value to t, since I
> can change it to nil in .emacs. But there is no way to ignore the
> frame argument of `display-buffer' if it's specified explicitly.
If it really drives you nuts, make a special variable for this case or
something. But please don't change the existing behavior.
-Miles
--
I'd rather be consing.
next prev parent reply other threads:[~2004-05-13 7:28 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-09 0:44 next-error-last-buffer Juri Linkov
2004-05-09 18:47 ` next-error-last-buffer Richard Stallman
2004-05-09 23:32 ` next-error-last-buffer Juri Linkov
2004-05-10 17:54 ` next-error-last-buffer Richard Stallman
2004-05-10 18:28 ` next-error-last-buffer Stefan Monnier
2004-05-10 23:45 ` next-error-last-buffer Juri Linkov
2004-05-11 12:23 ` next-error-last-buffer Richard Stallman
2004-05-10 23:35 ` next-error-last-buffer Juri Linkov
2004-05-11 2:19 ` next-error-last-buffer Stefan Monnier
2004-05-11 15:36 ` next-error-last-buffer Ted Zlatanov
2004-05-11 23:46 ` next-error-last-buffer Juri Linkov
2004-05-12 13:50 ` next-error-last-buffer Ted Zlatanov
2004-05-13 4:15 ` next-error-last-buffer Juri Linkov
2004-05-13 13:01 ` next-error-last-buffer Ted Zlatanov
2004-05-12 19:42 ` next-error-last-buffer Richard Stallman
2004-05-13 4:23 ` next-error-last-buffer Juri Linkov
2004-05-13 4:57 ` next-error-last-buffer Miles Bader
2004-05-13 5:17 ` next-error-last-buffer Stefan Monnier
2004-05-13 5:34 ` next-error-last-buffer Juri Linkov
2004-05-13 7:28 ` Miles Bader [this message]
2004-05-13 12:54 ` next-error-last-buffer Ted Zlatanov
2004-05-14 9:21 ` next-error-last-buffer Richard Stallman
2004-05-14 14:58 ` next-error-last-buffer Ted Zlatanov
2004-05-15 8:21 ` next-error-last-buffer Juri Linkov
2004-05-15 18:34 ` next-error-last-buffer Richard Stallman
2004-05-15 8:53 ` next-error-last-buffer Richard Stallman
2004-05-24 8:46 ` next-error-last-buffer Juri Linkov
2004-05-24 14:16 ` next-error-last-buffer Ted Zlatanov
2004-05-25 20:09 ` next-error-last-buffer Juri Linkov
2004-05-26 13:49 ` next-error-last-buffer Ted Zlatanov
2004-05-27 12:46 ` next-error-last-buffer Richard Stallman
2004-05-28 15:38 ` next-error-last-buffer Ted Zlatanov
2004-05-28 21:07 ` next-error-last-buffer Juri Linkov
2004-05-29 3:47 ` next-error-last-buffer Ted Zlatanov
2004-05-30 14:30 ` next-error-last-buffer Richard Stallman
2004-06-01 17:41 ` next-error-last-buffer Ted Zlatanov
2004-06-01 17:57 ` next-error-last-buffer Ted Zlatanov
2004-06-02 17:36 ` next-error-last-buffer Richard Stallman
2004-06-03 15:21 ` next-error-last-buffer Ted Zlatanov
2004-06-04 2:03 ` next-error-last-buffer Richard Stallman
2004-06-07 16:18 ` next-error-last-buffer Ted Zlatanov
2004-06-08 20:31 ` next-error-last-buffer Richard Stallman
2004-06-30 18:38 ` next-error-last-buffer Ted Zlatanov
2004-07-01 17:14 ` next-error-last-buffer Richard Stallman
2004-05-25 16:06 ` next-error-last-buffer Richard Stallman
2004-05-25 20:14 ` next-error-last-buffer Juri Linkov
2004-05-26 13:56 ` next-error-last-buffer Ted Zlatanov
2004-05-27 21:55 ` next-error-last-buffer Juri Linkov
2004-05-27 23:53 ` next-error-last-buffer Richard Stallman
2004-05-28 15:29 ` next-error-last-buffer Stefan Monnier
2004-05-28 21:55 ` next-error-last-buffer Juri Linkov
2004-05-29 3:35 ` next-error-last-buffer Ted Zlatanov
2004-05-29 17:03 ` next-error-last-buffer Richard Stallman
2004-05-25 20:22 ` next-error-last-buffer Juri Linkov
2004-05-29 1:44 ` next-error-last-buffer Richard Stallman
2004-05-29 23:10 ` next-error-last-buffer Kim F. Storm
2004-05-30 19:41 ` next-error-last-buffer Richard Stallman
2004-05-31 6:39 ` next-error-last-buffer Werner LEMBERG
2004-05-31 7:20 ` next-error-last-buffer Juanma Barranquero
2004-06-01 17:52 ` next-error-last-buffer Ted Zlatanov
2004-06-01 21:33 ` next-error-last-buffer Kim F. Storm
2004-06-02 17:36 ` next-error-last-buffer Richard Stallman
2004-06-03 23:42 ` next-error-last-buffer Juri Linkov
2004-06-05 13:48 ` next-error-last-buffer 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=buo3c643hwv.fsf@mctpc71.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=rms@gnu.org \
--cc=tzz@lifelogs.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).