unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Subject: same-window-buffer-names and -regexps
Date: Mon, 19 Aug 2002 21:43:23 -0500 (CDT)	[thread overview]
Message-ID: <200208200243.VAA04929@eel.dms.auburn.edu> (raw)

There seems to be an obvious anomaly in the behavior of the
display-buffer - same-window-buffer-names (-regexps) mechanism.  It
works fine for commands such as M-x shell and the like, but what sense
does it make for C-x 4 C-o to behave specially for the buffers in
question?  For these buffers, C-x 4 C-o behaves like C-x b.  If that
were the behavior the user wanted, (s)he would clearly use the easier
and more logical command C-x b.  Same thing for the command C-o in the
buffer menu, which for these buffers is identical to f.  The effect on
C-c C-f in ielm is even worse.  I guess there must be several other
additional situations like this.  This behavior is both inconvenient
and extremely confusing.  Somebody who does not know about these two
variables does not stand the slightest chance of figuring out the
cause of all this strange behavior.

Setting the two variables to nil is no solution, because then M-x
shell and friends malfunction.

One solution would be to have M-x shell and friends check these
variables (instead of having display-buffer do that directly) and
then have these functions pass an appropriate flag to display-buffer.

Sincerely,

Luc.

             reply	other threads:[~2002-08-20  2:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20  2:43 Luc Teirlinck [this message]
2002-08-20  2:52 ` same-window-buffer-names and -regexps Miles Bader
2002-08-20  3:16   ` Luc Teirlinck
2002-08-20  3:25     ` Miles Bader
2002-08-20  4:09       ` Luc Teirlinck
2002-08-21  0:12       ` Richard Stallman
2002-08-20 16:24 ` Stefan Monnier

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=200208200243.VAA04929@eel.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    /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).