From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: germanp82@hotmail.com, 68081@debbugs.gnu.org
Subject: bug#68081: 30.0.50; derived-mode and display-buffer-alist
Date: Thu, 04 Jan 2024 12:39:33 +0200 [thread overview]
Message-ID: <835y09xtzu.fsf@gnu.org> (raw)
In-Reply-To: <c56fcfbe-ceeb-425a-bfdc-ad1ff3e1eb77@gmx.at> (message from martin rudalics on Thu, 4 Jan 2024 11:21:17 +0100)
> Date: Thu, 4 Jan 2024 11:21:17 +0100
> Cc: germanp82@hotmail.com, 68081@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
>
> >> 'info' initially used 'switch-to-buffer'
> >>
> >> (if (get-buffer "*info*")
> >> (switch-to-buffer "*info*")
> >> (Info-directory))))
> >>
> >> Later it called 'pop-to-buffer' as
> >>
> >> (if (get-buffer "*info*")
> >> (pop-to-buffer "*info*")
> >> (Info-directory))))
> >>
> >> The breakage occurred when it started to call
> >>
> >> (pop-to-buffer "*info*")
> >>
> >> without checking whether that buffer exists. It sometimes backfires to
> >> use a feature meant for interactive use (like 'pop-to-buffer' creating
> >> its buffer autonomously) in non-interactive calls. Sometimes it happens
> >> decades after that feature was misused.
> >
> > Do other places that are affected by the same change do the same
> > mistake of unconditionally calling pop-to-buffer?
>
> Maybe my formulation was not clear. Basically, all calls of 'info'
> without first argument are affected by the change.
Thanks, but I was asking about callers of pop-to-buffer other than
'info'. German said in
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=68081#26 that other
callers, in addition to 'info' are also affected.
next prev parent reply other threads:[~2024-01-04 10:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 13:26 bug#68081: 30.0.50; derived-mode and display-buffer-alist German Pacenza
2023-12-28 14:07 ` Eli Zaretskii
2023-12-29 9:02 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-29 11:41 ` Eli Zaretskii
2023-12-30 9:30 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-30 10:12 ` Eli Zaretskii
2023-12-31 8:57 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-31 10:30 ` German Pacenza
2024-01-01 9:38 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-01 12:17 ` Eli Zaretskii
2024-01-02 10:46 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-03 11:59 ` Eli Zaretskii
2024-01-04 10:21 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-04 10:39 ` Eli Zaretskii [this message]
2024-01-05 9:22 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-05 10:18 ` German Pacenza
2024-01-06 8:56 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-06 10:35 ` German Pacenza
2024-01-06 11:39 ` Eli Zaretskii
2024-01-06 11:55 ` German Pacenza
2024-01-06 12:01 ` Eli Zaretskii
2024-01-13 9:30 ` Eli Zaretskii
2024-01-03 10:35 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-03 13:22 ` Eli Zaretskii
2024-01-04 10:21 ` martin rudalics via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-01-06 9:50 ` Eli Zaretskii
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=835y09xtzu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68081@debbugs.gnu.org \
--cc=germanp82@hotmail.com \
--cc=rudalics@gmx.at \
/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).