From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 70382@debbugs.gnu.org, matt@excalamus.com, juri@linkov.net
Subject: bug#70382: 29.3; Info-fontify-node renders cross-references misleadingly
Date: Sun, 14 Apr 2024 22:16:13 +0300 [thread overview]
Message-ID: <861q77n4aq.fsf@gnu.org> (raw)
In-Reply-To: <jwv34rnx0hu.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 14 Apr 2024 14:43:31 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: matt@excalamus.com, Juri Linkov <juri@linkov.net>, 70382@debbugs.gnu.org
> Date: Sun, 14 Apr 2024 14:43:31 -0400
>
> > 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.
> > Juri and Stefan, do you see a cleaner solution?
>
> We could try and detect that the cross ref is within a '...'.
That would fail in other cases.
> BTW, I'm not sure whether the current behavior is really a problem:
> after all, in Emacs, people indeed won't see something of the form
> `*note NAME: NODE.` but they'll see something of the form `see NAME` or
> `See NAME`, so the bug could be considered a feature (depending on
> whether we think the doc describes the content of the Info file or
> whether it describes when readers will see when reading their doc in
> Emacs).
Yes, but here we make worse mistakes: not only we should "see" with
wrong capitalization, we also make the impression that @ref shows as
"see" in Emacs (it doesn't) and @pxref shows "*note" (it shows "see").
(I think the text should have a note that in Emacs these
cross-references will look differently, but that's a patch to be
submitted to the Texinfo developers.)
next prev parent reply other threads:[~2024-04-14 19:16 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 [this message]
2024-04-15 6:55 ` Juri Linkov
2024-04-15 11:39 ` Eli Zaretskii
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
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=861q77n4aq.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 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).