GNU bug report logs -
#55582
29.0.50; switch-to-buffer-other-tab doesn't set the buffer
Previous Next
Reported by: Sean Whitton <spwhitton <at> spwhitton.name>
Date: Sun, 22 May 2022 19:45:01 UTC
Severity: normal
Found in version 29.1
Fixed in version 29.0.50
Done: Juri Linkov <juri <at> jurta.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 55582 in the body.
You can then email your comments to 55582 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
juri <at> jurta.org, bug-gnu-emacs <at> gnu.org
:
bug#55582
; Package
emacs
.
(Sun, 22 May 2022 19:45:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Sean Whitton <spwhitton <at> spwhitton.name>
:
New bug report received and forwarded. Copy sent to
juri <at> jurta.org, bug-gnu-emacs <at> gnu.org
.
(Sun, 22 May 2022 19:45:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
1. emacs -q
2. M-: (progn (switch-to-buffer-other-tab "*Messages*") (buffer-name))
- Actual result: "*GNU Emacs*" in echo area.
- Expected result: "*Messages*" in echo area.
You can work around it by calling set-buffer right after
switch-to-buffer-other-tab, but that shouldn't be necessary.
The other switch-to-buffer-... functions all set the buffer correctly.
--
Sean Whitton
Changed bug title to '29.0.50; switch-to-buffer-other-tab doesn't set the buffer' from '29.1; switch-to-buffer-other-tab doesn't set the buffer'
Request was from
Sean Whitton <spwhitton <at> spwhitton.name>
to
control <at> debbugs.gnu.org
.
(Sun, 22 May 2022 21:25:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#55582
; Package
emacs
.
(Mon, 23 May 2022 02:24:01 GMT)
Full text and
rfc822 format available.
Message #10 received at 55582 <at> debbugs.gnu.org (full text, mbox):
> Cc: juri <at> jurta.org
> From: Sean Whitton <spwhitton <at> spwhitton.name>
> Date: Sun, 22 May 2022 12:44:42 -0700
>
> 1. emacs -q
> 2. M-: (progn (switch-to-buffer-other-tab "*Messages*") (buffer-name))
> - Actual result: "*GNU Emacs*" in echo area.
> - Expected result: "*Messages*" in echo area.
Can you explain why you expected to see "*Messages*" in this case?
What kind of documentation says this is what should happen?
Thanks.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#55582
; Package
emacs
.
(Mon, 23 May 2022 04:51:01 GMT)
Full text and
rfc822 format available.
Message #13 received at 55582 <at> debbugs.gnu.org (full text, mbox):
Hello,
On Mon 23 May 2022 at 05:22am +03, Eli Zaretskii wrote:
>> Cc: juri <at> jurta.org
>> From: Sean Whitton <spwhitton <at> spwhitton.name>
>> Date: Sun, 22 May 2022 12:44:42 -0700
>>
>> 1. emacs -q
>> 2. M-: (progn (switch-to-buffer-other-tab "*Messages*") (buffer-name))
>> - Actual result: "*GNU Emacs*" in echo area.
>> - Expected result: "*Messages*" in echo area.
>
> Can you explain why you expected to see "*Messages*" in this case?
All the other pop-to-* and switch-to-* functions set the buffer, and the
language "switch to buffer" in Emacs includes making the target buffer
current.
I can't see any reason why switch-to-buffer-other-tab should be
different from its fellows.
> What kind of documentation says this is what should happen?
The documentation for switch-to-buffer-other-tab says that it is "Like
C-x 5 b", and switch-to-buffer-other-frame makes the target buffer
current.
--
Sean Whitton
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#55582
; Package
emacs
.
(Mon, 23 May 2022 07:51:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 55582 <at> debbugs.gnu.org (full text, mbox):
close 55582 29.0.50
thanks
> 1. emacs -q
> 2. M-: (progn (switch-to-buffer-other-tab "*Messages*") (buffer-name))
> - Actual result: "*GNU Emacs*" in echo area.
> - Expected result: "*Messages*" in echo area.
>
> You can work around it by calling set-buffer right after
> switch-to-buffer-other-tab, but that shouldn't be necessary.
> The other switch-to-buffer-... functions all set the buffer correctly.
Both switch-to-buffer-other-window and switch-to-buffer-other-frame
use pop-to-buffer, but it was unnecessary for switch-to-buffer-other-tab
since it sets the current buffer implicitly afterwards.
But you are right, this causes the problems on a programmatic use
of this command. So now this is fixed in master.
bug marked as fixed in version 29.0.50, send any further explanations to
55582 <at> debbugs.gnu.org and Sean Whitton <spwhitton <at> spwhitton.name>
Request was from
Juri Linkov <juri <at> jurta.org>
to
control <at> debbugs.gnu.org
.
(Mon, 23 May 2022 07:51:03 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Mon, 20 Jun 2022 11:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 309 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.