From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31125-done@debbugs.gnu.org
Subject: bug#31125: 26; (emacs) `Highlight Interactively'
Date: Wed, 11 Apr 2018 21:37:50 -0700 (PDT) [thread overview]
Message-ID: <128680b7-eb89-42ec-9013-a99120d6d8f8@default> (raw)
In-Reply-To: <<83a7u92m60.fsf@gnu.org>>
> > (It does somehow seem to bad that someone can read the
> > entire Emacs manual without knowing anything about
> > Lisp symbols, including that there is such a critter.)
>
> Actually, "Symbol Search", which is where you get if you select
> "symbol search" from the completion list popped up by "i search TAB",
> does try to tell what is a symbol in language-independent terms.
Yes, I'm aware of that. And that additional, syntactic
meaning of "symbol" in Emacs jargon has little-to-nothing
to do with Lisp symbols.
A reader won't learn anything about Lisp symbols by
reading that node. On the contrary: s?he will instead
mislearn something untrue that suggests it is about Lisp
symbols but is not.
A Lisp symbol is not just "a source code token", nor are
Lisp-mode "source code tokens" necessarily Lisp symbols.
Using `forward-symbol' or "symbol search" in Lisp does
not move across or find Lisp symbols.
It's too bad that Emacs chose to appropriate the term
"symbol" for that other, essentially unrelated meaning.
But it did. It's a shame because Lisp is something
really important to Emacs, and so to Emacs users. And
symbols are something important to Lisp.
This is what Lisp symbols are about (though they have
additional characteristics):
https://en.wikipedia.org/wiki/Symbol_(programming)
next parent reply other threads:[~2018-04-12 4:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<57ad2ae3-cfe5-4fca-a503-e106658d3e38@default>
[not found] ` <<<83efjl3cyk.fsf@gnu.org>
[not found] ` <<5b84d18a-5781-4ab9-8593-5db385574556@default>
[not found] ` <<83a7u92m60.fsf@gnu.org>
2018-04-12 4:37 ` Drew Adams [this message]
2018-04-12 11:38 ` bug#31125: 26; (emacs) `Highlight Interactively' Eli Zaretskii
2018-04-12 14:27 ` Drew Adams
[not found] <<57ad2ae3-cfe5-4fca-a503-e106658d3e38@default>
[not found] ` <<83efjl3cyk.fsf@gnu.org>
2018-04-11 19:41 ` Drew Adams
2018-04-12 2:28 ` Eli Zaretskii
2018-04-11 14:45 Drew Adams
2018-04-11 16:49 ` Eli Zaretskii
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=128680b7-eb89-42ec-9013-a99120d6d8f8@default \
--to=drew.adams@oracle.com \
--cc=31125-done@debbugs.gnu.org \
--cc=eliz@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 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).