unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: germanp82@hotmail.com, 68081@debbugs.gnu.org
Subject: bug#68081: 30.0.50; derived-mode and display-buffer-alist
Date: Thu, 4 Jan 2024 11:21:39 +0100	[thread overview]
Message-ID: <aa4bd405-3f06-4aba-b46d-3f06d2a39824@gmx.at> (raw)
In-Reply-To: <8334vezh4d.fsf@gnu.org>

 > Thanks.  This is a significant change, so probably not suitable for
 > the release branch.  Do you think the simple change of using the old
 >
 >       (if (get-buffer "*info*")
 > 	(pop-to-buffer "*info*")
 >         (Info-directory))))
 >
 > is okay for installing on the release branch,

Where would we do that?  The context for that snippet has vanished long
ago and we need a buffer we can pass to 'info-setup'.

 > or would you recommend
 > to leave the release branch without a fix and only fix this on master?

Only fix this on master.  The warning for 'buffer-match-p' would be
needed for both - release branch and master - anyway.  Who knows how
many cases similar to this we have.

martin





  reply	other threads:[~2024-01-04 10:21 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
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 [this message]
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=aa4bd405-3f06-4aba-b46d-3f06d2a39824@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 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).