From: martin rudalics via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: German Pacenza <germanp82@hotmail.com>
Cc: 68081@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#68081: 30.0.50; derived-mode and display-buffer-alist
Date: Mon, 1 Jan 2024 10:38:09 +0100 [thread overview]
Message-ID: <8db30606-c98c-4078-a448-6ad31bd59768@gmx.at> (raw)
In-Reply-To: <MW4PR20MB510530AA03A2D0A529390028A763A@MW4PR20MB5105.namprd20.prod.outlook.com>
> I agree, Info mode is only one of the affected modes, compilation-mode
> also shows this behaviour and others might as well.
And these cannot be reasonably fixed all by moving the -mode calls in
front of the 'display-buffer' call in a consistent manner.
The original problem is with 'window-normalize-buffer-to-switch-to'. It
should never be called in non-interactive use, so 'info' would have been
forced to provide a buffer as argument and not just a name.
I'm afraid that this inconsistency makes 'buffer-match-p' pretty useless
for 'pop-to-buffer' and its like. A strong warning seems appropriate.
martin
next prev parent reply other threads:[~2024-01-01 9:38 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8db30606-c98c-4078-a448-6ad31bd59768@gmx.at \
--to=bug-gnu-emacs@gnu.org \
--cc=68081@debbugs.gnu.org \
--cc=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.