From: Eli Zaretskii <eliz@gnu.org>
To: Dan Jacobson <jidanni@jidanni.org>
Cc: 71220@debbugs.gnu.org
Subject: bug#71220: Missing hyperlink
Date: Mon, 27 May 2024 14:39:31 +0300 [thread overview]
Message-ID: <86ttijv5zg.fsf@gnu.org> (raw)
In-Reply-To: <87v82zhdoj.7.fsf@jidanni.org> (message from Dan Jacobson on Mon, 27 May 2024 16:17:00 +0800)
> From: Dan Jacobson <jidanni@jidanni.org>
> Date: Mon, 27 May 2024 16:17:00 +0800
>
> (info "(emacs) Fixing Case") contains a hyperlink to
> (info "(emacs) Case") but the latter is missing a vital hyperlink to the former!!
> I'm saying if we are reading the latter, we would feel sad if we found out one day we didn't know about the former.
I don't understand: "Case" tells everything that "Fixing Case" tells,
and then some. By contrast, "Fixing Case" describes only a small part
of what "Case" describes, and it does that to avoid the need for the
reader to read the entire large section in "Case" when all they are
interested in is how to fix letter-case typos.
If we added a cross-reference to "Case" to "Fixing Case", what would
that add to what "Case" already describes? If it doesn't add
anything, then a reverse cross-reference would not be useful.
next prev parent reply other threads:[~2024-05-27 11:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 8:17 bug#71220: Missing hyperlink Dan Jacobson
2024-05-27 11:39 ` Eli Zaretskii [this message]
2024-05-27 13:41 ` Dan Jacobson
2024-05-27 13:59 ` Eli Zaretskii
2024-05-27 14:43 ` Dan Jacobson
2024-05-28 12:40 ` Eli Zaretskii
2024-05-27 21:04 ` Stefan Kangas
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=86ttijv5zg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71220@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
/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).