From: Lars Ingebrigtsen <larsi@gnus.org>
To: Juri Linkov <juri@jurta.org>
Cc: 23131@debbugs.gnu.org, jan <rtm443x@googlemail.com>
Subject: bug#23131: switch-to-buffer-other-frame problem
Date: Wed, 14 Jul 2021 16:46:24 +0200 [thread overview]
Message-ID: <87eec1hs1r.fsf@gnus.org> (raw)
In-Reply-To: <87a8ld6reb.fsf@mail.linkov.net> (Juri Linkov's message of "Fri, 01 Apr 2016 22:49:32 +0300")
Juri Linkov <juri@jurta.org> writes:
>>> 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?
>
> This change was discussed here where you can see all arguments pro and contra:
> http://thread.gmane.org/gmane.emacs.devel/93054/focus=95497
So I think this works as designed. We could perhaps mention
`read-buffer-to-switch' in the interactive case in the doc strings, but
I think that's a level of detail that'd just be counter-productive, so
I'd rather not, and I'm closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2021-07-14 14:46 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
2016-04-01 19:49 ` Juri Linkov
2021-07-14 14:46 ` Lars Ingebrigtsen [this message]
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=87eec1hs1r.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=23131@debbugs.gnu.org \
--cc=juri@jurta.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).