From: Drew Adams <drew.adams@oracle.com>
To: tomas@tuxteam.de, help-gnu-emacs@gnu.org
Subject: RE: Path of tool-bar icons
Date: Wed, 11 Apr 2018 14:47:39 -0700 (PDT) [thread overview]
Message-ID: <8d731b35-3056-47fd-a542-9aeff81bf855@default> (raw)
In-Reply-To: <20180411205539.GE26644@tuxteam.de>
<user looks for "icon" instead of what Emacs expects: "image">
> > > This is a difficult thing in Emacs: it has
> > > its own (strong) culture and its lexicon
> > > sometimes differs in subtle ways from
> > > people's expectations.
> >
> > There are a couple of such cases but it isn't
> > epidemic like some people like to exaggerate,
> > often to push the "Emacs is difficult to learn"
> > notion, likewise exaggerated. There was a guy on
> > this list who made a big hullabaloo of some
> > window/frame issue for example...
>
> I think it *is* a hurdle. I don't think changing Emacs'
> culture is a solution to that (nor that it's desirable,
> for that). But I do think it helps being aware of it.
1. `C-h r'
`i glossary'
(or `g glossary', if you know there is a node named Glossary)
If you want to suggest a common term to add to the glossary,
to xref a more traditional Emacs term, even if the two are
not exactly synonymous, you can do that: `M-x report-emacs-bug'.
For example, search the glossary for "paste" and you'll
find this entry:
Cut and Paste
see Glossary--Killing, and see Glossary--Yanking
Those are links, after "see". They should take you to the
glossary entries "killing" and "yanking", respectively.
Unfortunately, a regression was apparently introduced in
Emacs 24.5 - those links now take you elsewhere. I just
filed bug #31130 for this.
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=31130
(The fact that this regression has apparently gone
unnoticed since Emacs 24.5 maybe indicates how little use
people make of at least some glossary entries, if not the
glossary itself.)
2. There is also this page on Emacs Wiki:
https://www.emacswiki.org/emacs/EmacsJargon
3. However, I'm not sure that this problem of
looking-for-"icon"-instead-of-"image" is really a
problem of Emacs using uncommon jargon. I'd think
that it's kinda natural to look for "image" if "icon"
finds no hits wrt the tool bar.
next prev parent reply other threads:[~2018-04-11 21:47 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 [this message]
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
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
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=8d731b35-3056-47fd-a542-9aeff81bf855@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tomas@tuxteam.de \
/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.
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).