From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: 70382@debbugs.gnu.org, monnier@iro.umontreal.ca, matt@excalamus.com
Subject: bug#70382: 29.3; Info-fontify-node renders cross-references misleadingly
Date: Mon, 15 Apr 2024 14:39:02 +0300 [thread overview]
Message-ID: <86mspulusp.fsf@gnu.org> (raw)
In-Reply-To: <86y19fp0ls.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 15 Apr 2024 09:55:19 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>, matt@excalamus.com,
> 70382@debbugs.gnu.org
> Date: Mon, 15 Apr 2024 09:55:19 +0300
>
> >> > I think the only sane way of dealing with this problem is to disable
> >> > Info-hide-note-references in that particular node (and any other
> >> > nodes, if we find them, where there's a similar issue). The patch
> >> > below attempts to do that.
> >>
> >> Sounds OK.
> >
> > OK, I will install this soon, unless Juri (or someone else) comes up
> > with something more elegant.
>
> Like many self-reference cases this needs an exception too, so probably
> there is no better way than info--dont-hide-references (maybe this name
> should be upper-cased to Info--dont-hide-references like other Info variables).
I named it "info--*" so that this internal variable doesn't get in the
way when one completes on Info variable names. But I see now that we
already have quite a few internal names that start with "Info--", so I
guess that ship has sailed long ago.
Thanks for the feedback, will install soon.
next prev parent reply other threads:[~2024-04-15 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-14 14:35 bug#70382: 29.3; Info-fontify-node renders cross-references misleadingly Matt
2024-04-14 16:21 ` Eli Zaretskii
2024-04-14 18:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-14 19:16 ` Eli Zaretskii
2024-04-15 6:55 ` Juri Linkov
2024-04-15 11:39 ` Eli Zaretskii [this message]
2024-04-15 12:49 ` 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=86mspulusp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70382@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=matt@excalamus.com \
--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.