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: Fri, 29 Dec 2023 13:41:36 +0200 [thread overview]
Message-ID: <83v88h5j7z.fsf@gnu.org> (raw)
In-Reply-To: <342c493e-b0ba-40a8-8023-58a9bb04abd6@gmx.at> (message from martin rudalics on Fri, 29 Dec 2023 10:02:50 +0100)
> Date: Fri, 29 Dec 2023 10:02:50 +0100
> Cc: 68081@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
>
> >> display-buffer-alist rules that use derived-mode or major-mode are
> >> ignored on first use.
> >>
> >> emacs -Q:
> >>
> >> (setq display-buffer-alist '(((derived-mode . Info-mode)
> >> (display-buffer-in-side-window))))
> >> "C-h i"
> >> The info buffer takes the whole window
> >> "q"
> >> "C-h i"
> >> The info buffer opens in side window as expected
> >>
> >> Info and Compilation modes are affected, but Help and Man work as expected
> >
> > Martin, any comments or suggestions?
>
> C-h i does
>
> (info-setup file-or-node
> (pop-to-buffer-same-window (or buffer "*info*"))))
>
> In the first call BUFFER is nil and the
>
> (provided-mode-derived-p
> (buffer-local-value 'major-mode buffer)
> mode))
>
> rigmarole in 'buffer-match-p' won't report a match because the major
> mode of *info* is still fundamental mode. In later calls the *info*
> buffer exists already, is in Info-mode, and 'buffer-match-p' will
> produce the desired result.
>
> We could try to call 'Info-mode' _before_ calling 'display-buffer' but
> I'm not sure of the consequences this would have.
Thanks. I tend to document this subtlety, and otherwise leave it
alone.
next prev parent reply other threads:[~2023-12-29 11:41 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 [this message]
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
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=83v88h5j7z.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 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.