From: martin rudalics <rudalics@gmx.at>
To: jan <rtm443x@googlemail.com>
Cc: 23131@debbugs.gnu.org
Subject: bug#23131: switch-to-buffer-other-frame problem
Date: Tue, 29 Mar 2016 17:13:27 +0200 [thread overview]
Message-ID: <56FA9B97.5020807@gmx.at> (raw)
In-Reply-To: <CADJx9LeYT6Obs8Lg=yC0a0+=oU49La7QTje=Di39shGF4qG1aA@mail.gmail.com>
>> If, in this situation, you type C-x b, Emacs won't offer you sample.txt
>> as completion either. Ditto for ‘switch-to-buffer-other-window’.
>
> I'd say that replication of (arguably questionable) behaviour doesn't
> justify it.
We'll have to wait until the respective author(s) explain the reasons
for the change.
>> It's
>> difficult to say what the correct behavior should be. I never use the
>> buffer switching commands, so I have no preference. But I suppose that
>> some people would complain if C-x b offered them the buffer already
>> shown in the selected window as possible completion.
>
> Well, Eli Zaretski said of this (I'd emailed him first) "Yes, it's a
> feature: Emacs doesn't offer you a buffer that is already displayed in
> an existing window. This was introduced in Emacs 24."
IIUC it was introduced in Emacs 23.
> So it is new behaviour.
Relatively so, since I can reproduce it with a seven years old build.
If I'm not mistaken the change is by Juri Linkov from 2008-04-22.
> Therefore: 1) was it introduced deliberately? If so, why? (if the code
> was the code made more complex by introducing a special case rather
> than simplifiying it, doubly why?)
>
> And: 2) this behaviour is not documented. My understanding is that
> documentation omissions are considered bugs.
Juri, what do you think?
martin
next prev parent reply other threads:[~2016-03-29 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-27 23:37 bug#23131: switch-to-buffer-other-frame problem jan
2016-03-28 11:22 ` martin rudalics
2016-03-29 8:38 ` jan
2016-03-29 15:13 ` martin rudalics [this message]
2016-04-01 19:49 ` Juri Linkov
2021-07-14 14:46 ` Lars Ingebrigtsen
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=56FA9B97.5020807@gmx.at \
--to=rudalics@gmx.at \
--cc=23131@debbugs.gnu.org \
--cc=rtm443x@googlemail.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).