From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 62300@debbugs.gnu.org
Subject: bug#62300: 29.0.60; No hyperlinks for some symbols in *Help* buffers
Date: Tue, 21 Mar 2023 21:54:24 +0200 [thread overview]
Message-ID: <834jqd7udr.fsf@gnu.org> (raw)
In-Reply-To: <jwvwn3adixf.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 21 Mar 2023 15:09:00 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: 62300@debbugs.gnu.org
> Date: Tue, 21 Mar 2023 15:09:00 -0400
>
> >> E.g. with the patch below.
> > Thanks. Do you consider this safe enough for the emacs-29 branch?
>
> The risk is very small, but the gain is also very small (the problem
> is definitely not a regression: AFAICT this is unchanged since Emacs-26
> and before that the result was more consistent but with fewer links).
>
> I'd keep it on `master`, personally.
OK, master it is, then.
next prev parent reply other threads:[~2023-03-21 19:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 18:34 bug#62300: 29.0.60; No hyperlinks for some symbols in *Help* buffers Eli Zaretskii
2023-03-20 18:52 ` Eli Zaretskii
2023-03-20 21:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-21 13:11 ` Eli Zaretskii
2023-03-21 14:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-21 17:26 ` Eli Zaretskii
2023-03-21 17:59 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-21 18:23 ` Eli Zaretskii
2023-03-21 19:09 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-21 19:54 ` Eli Zaretskii [this message]
2023-03-22 1:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-22 15:52 ` 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=834jqd7udr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=62300@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.