From: "Drew Adams" <drew.adams@oracle.com>
To: "Emacs-Devel" <emacs-devel@gnu.org>
Subject: links in *Apropos* buffer
Date: Sat, 22 Sep 2007 16:02:40 -0700 [thread overview]
Message-ID: <DHEEKFAFJEFOJHLCFPFDMEDJCBAA.drew.adams@oracle.com> (raw)
There is duplication in the links of an *Apropos* buffer: the
command/function/macro/variable/plist/face name has a link that is identical
to one of the links below it (Command, Function, etc.). Apparently, it is
the first such link that is duplicated. And most apropos entries have only
one link below them (they are only a command or only a variable etc.), so
this is nearly 100% duplication.
A user will click both the command name and the word "Command" to see what
they point to, and will discover that they are the same thing.
I propose that we do away with this duplication. Here are some possibilities
(alternatives):
1. Just remove the link on the command etc. name.
2. Have the link on the command etc. name take you to its treatment in an
appropriate manual (for a command, it would do
`Info-goto-emacs-command-node', for instance). Since there might be several
such entries, this might actually access the relevant index entries or it
could do as `Info-goto-emacs-command-node' does (put other entries in
`Info-history').
3. Have the link on the command etc. name take you to the source code that
defines it. As now, whenever there are multiple entries for the same name
(e.g. function, variable, face), the definition of the first of these would
be used. It could be argued that a link on the entry name is too prominent
to send you to source code, especially C code.
I vote for #2. If that's not feasible, then #1.
next reply other threads:[~2007-09-22 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 23:02 Drew Adams [this message]
2007-09-23 15:05 ` links in *Apropos* buffer Richard Stallman
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=DHEEKFAFJEFOJHLCFPFDMEDJCBAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.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 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.