From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "larsi@gnus.org" <larsi@gnus.org>,
"50760@debbugs.gnu.org" <50760@debbugs.gnu.org>
Subject: bug#50760: [External] : Re: bug#50760: 26.3; Add `symbol' to the Emacs manul glossary
Date: Fri, 24 Sep 2021 18:53:17 +0000 [thread overview]
Message-ID: <SJ0PR10MB54886509CC948CC9B9EC8696F3A49@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83lf3mtscj.fsf@gnu.org>
> > There are (at least) two important meanings of "symbol" in Emacs:
> >
> > 1. The usual Lisp meaning, which is meaningful only in Lisp.
> >
> > 2. The Elisp meaning of characters with symbol-constituent syntax.
> And perhaps names composed of such chars, possibly combined with chars
> with other syntax, e.g., typically word-constituent.
> >
> > For example, in programming languages (not only Elisp), we have
> commands such as `forward-symbol'. They move over or otherwise
> manipulate names composed of symbol-constituent chars and sometimes
> other kinds of chars.
> >
> > Emacs users deserve to know about these quite different meanings, I
> think. Each such meaning is important to using Emacs.
>
> The meaning of "symbol" for searching is explained in "Symbol Search".
Great. Add that meaning to the glossary entry, please.
(And it's also movement commands, not just search.)
A user seeing the doc string for `C-h S'
(`info-lookup-symbol') can well wonder what "symbol"
means.
My observation comes from someone having questioned
possibly using the word "symbol" in a help menu item
(for `info-lookup-symbol'). The term isn't obvious,
especially for new users.
prev parent reply other threads:[~2021-09-24 18:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 14:41 bug#50760: 26.3; Add `symbol' to the Emacs manul glossary Drew Adams
2021-09-23 21:34 ` Lars Ingebrigtsen
2021-09-23 22:14 ` bug#50760: [External] : " Drew Adams
2021-09-24 6:12 ` Eli Zaretskii
2021-09-24 18:53 ` Drew Adams [this message]
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=SJ0PR10MB54886509CC948CC9B9EC8696F3A49@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=50760@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.