From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <moasen@zoho.com>, help-gnu-emacs@gnu.org
Subject: RE: Path of tool-bar icons
Date: Wed, 11 Apr 2018 15:23:45 -0700 (PDT) [thread overview]
Message-ID: <0e2cbbd3-d5d6-4c60-baea-6f475ad4cf9c@default> (raw)
In-Reply-To: <86vacxe75d.fsf@zoho.com>
> > <user looks for "icon" instead of what Emacs
> > expects: "image">
> > [...]
> > 1. `C-h r'
> >
> > `i glossary'
> > (or `g glossary', if you know there is a node
> > named Glossary)
>
> So ?
1. My point was that if someone really thinks that some
Emacs users will think only "icon" and never "image"
in this context, and it is a sufficiently important
problem, they can ask that the two terms be added to
the glossary and linked there. Emacs jargon uses
"yank", but newbies can find it under "paste" in the
glossary.
(Personally, I can't imagine not thinking of looking
for "image" if I didn't find what I was looking for
under "icon". But users look for things differently,
and users have different vocabularies and mental
models.)
Even without bringing the glossary into it (and this
is a case where the glossary is not really relevant,
I think - "image" is not really Emacs jargon), you
could request an _index_ entry for "icon" that links
to where `image-load-path' is discussed.
2. But that variable is covered only in the Elisp
manual, not the Emacs manual. There is an index entry
for it, but index entries that contain substring "icon"
don't lead there. So if someone thought this was a real
discovery problem s?he could request an index entry in
the Elisp manual for "icon file locations" or some such,
which would take you to the same node (`Defining Images').
3. But it is true that if something is not in one
of the manuals then there is no equivalent of indexing
or a glossary. (But you can google or search Emacs Wiki.)
You can search doc strings or use apropos commands,
including `apropos-documentation', but that just
searches doc strings literally. It doesn't take advantage
of someone having created an explicit link (xref) between
"icon" and "image".
next prev parent reply other threads:[~2018-04-11 22:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 8:13 Path of tool-bar icons Mick Bert
2018-04-11 11:39 ` Arkadiusz Drabczyk
2018-04-11 14:01 ` Mick Bert
2018-04-11 14:36 ` Arkadiusz Drabczyk
2018-04-11 15:27 ` tomas
2018-04-11 16:33 ` Eli Zaretskii
2018-04-11 18:42 ` tomas
2018-04-12 12:44 ` Eli Zaretskii
2018-04-12 12:49 ` tomas
[not found] ` <mailman.12056.1523472150.27995.help-gnu-emacs@gnu.org>
2018-04-11 20:38 ` Emanuel Berg
2018-04-11 20:55 ` tomas
2018-04-11 21:47 ` Drew Adams
2018-04-12 7:11 ` tomas
2018-04-12 11:26 ` Eli Zaretskii
2018-04-12 16:55 ` Drew Adams
[not found] ` <mailman.12074.1523483281.27995.help-gnu-emacs@gnu.org>
2018-04-11 21:59 ` Emanuel Berg
2018-04-11 22:23 ` Drew Adams [this message]
2018-04-12 12:18 ` Mick Bert
2018-04-12 12:39 ` Eli Zaretskii
[not found] ` <mailman.12043.1523464419.27995.help-gnu-emacs@gnu.org>
2018-04-11 17:05 ` Emanuel Berg
2018-04-11 17:29 ` Eli Zaretskii
[not found] ` <mailman.12050.1523467772.27995.help-gnu-emacs@gnu.org>
2018-04-11 20:33 ` Emanuel Berg
2018-04-12 12:39 ` Mick Bert
[not found] <mailman.12009.1523434449.27995.help-gnu-emacs@gnu.org>
2018-04-11 9:22 ` Emanuel Berg
2018-04-11 11:20 ` Mick Bert
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=0e2cbbd3-d5d6-4c60-baea-6f475ad4cf9c@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasen@zoho.com \
/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.