From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Kangas <stefan@marxist.se>
Cc: 16333@debbugs.gnu.org
Subject: bug#16333: 24.3.50; Info manuals: link defined terms to their glossary entries
Date: Wed, 15 Jan 2020 12:30:09 -0800 (PST) [thread overview]
Message-ID: <e1cd415e-7495-4344-807e-17f702582064@default> (raw)
In-Reply-To: <<835zhc4hor.fsf@gnu.org>>
> Our convention is to have index entries to all definitions. For
> example, type "i buffers RET", and you land where we define what is a
> buffer.
Yes, but that's not the same thing. There are many completions
of `i buffer TAB', and there's no indication that the `buffers'
one will take you to a definition. (An index entry like `buffer,
definition' would make that clear.)
In any case, the enhancement request explicitly acknowledged
that Emacs already provides ways to get to glossary items.
The request is to optionally highlight occurrences of the
term, so that you can notice that it's a glossary term and immediately jump to it from any context that uses it.
next parent reply other threads:[~2020-01-15 20:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<bc491f1f-4a8d-4953-a4aa-fd7c0121c1e6@default>
[not found] ` <<87pnfk1ozm.fsf@marxist.se>
[not found] ` <<835zhc4hor.fsf@gnu.org>
2020-01-15 20:30 ` Drew Adams [this message]
[not found] ` <<44a24b90-adf8-41f1-8d06-b35f55f1850c@default>
[not found] ` <<cbdf8d05-8ce5-4bc5-a04f-44c1e9b380db@default>
[not found] ` <<83tuudaz1y.fsf@gnu.org>
2020-10-29 17:51 ` bug#16333: 24.3.50; Info manuals: link defined terms to their glossary entries Drew Adams
2020-10-30 21:14 ` Drew Adams
2020-10-31 7:03 ` Eli Zaretskii
[not found] <<<bc491f1f-4a8d-4953-a4aa-fd7c0121c1e6@default>
[not found] ` <<<87pnfk1ozm.fsf@marxist.se>
[not found] ` <<<44a24b90-adf8-41f1-8d06-b35f55f1850c@default>
[not found] ` <<<cbdf8d05-8ce5-4bc5-a04f-44c1e9b380db@default>
[not found] ` <<<83tuudaz1y.fsf@gnu.org>
[not found] ` <<1f8767bb-1912-42ea-abba-dd666bea48b0@default>
[not found] ` <<3b9fabae-fbe4-4c4a-b11b-8aad73016ace@default>
[not found] ` <<83wnz698rr.fsf@gnu.org>
2020-10-31 17:04 ` Drew Adams
2014-01-03 21:50 Drew Adams
2020-01-15 19:47 ` Stefan Kangas
2020-01-15 19:56 ` Eli Zaretskii
2020-01-15 20:22 ` Drew Adams
2020-10-29 6:52 ` Drew Adams
2020-10-29 6:59 ` Drew Adams
2020-10-29 14:26 ` Eli Zaretskii
2020-10-29 14:40 ` Stefan Kangas
2020-10-29 18:13 ` Drew Adams
2021-10-11 14:02 ` Stefan Kangas
2021-10-11 14:05 ` Lars Ingebrigtsen
2021-10-11 14:32 ` Stefan Kangas
2021-10-11 14:34 ` Lars Ingebrigtsen
2021-10-11 14:55 ` 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=e1cd415e-7495-4344-807e-17f702582064@default \
--to=drew.adams@oracle.com \
--cc=16333@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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).