From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31125@debbugs.gnu.org
Subject: bug#31125: 26; (emacs) `Highlight Interactively'
Date: Thu, 12 Apr 2018 07:27:34 -0700 (PDT) [thread overview]
Message-ID: <314419b3-b645-40de-b3cd-be34956a7247@default> (raw)
In-Reply-To: <83zi281wpr.fsf@gnu.org>
> We were talking about the user manual, where the reader is not
> necessarily a Lisp programmer. For the latter, see "Symbols"
> in the ELisp manual.
You replied to my parenthetical remark after I said that
this bug can be closed, which was precisely about the
fact that the Emacs manual does not say anything about
Lisp symbols:
(It does somehow seem to[o] bad that someone can read
the entire Emacs manual without knowing anything about
Lisp symbols, including that there is such a critter.)
This particular discussion is not related to the bug
report, and it is exactly about the fact that the Emacs
manual does (too) little to guide users toward Lisp.
And some knowledge of Lisp is the single most important
aid and guide a user can have, to improve her experience
and use of Emacs.
This discussion is irrelevant to my (misguided) bug
report. But it is not irrelevant to the user manual.
A reader of the Emacs manual should not _need_ to
know Lisp to be able to read the manual. But that
doesn't mean the manual should keep completely
clear of Lisp. It could help, I think, for it to
occasionally point out some connections that can be
helpful for users.
next prev parent reply other threads:[~2018-04-12 14:27 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 ` bug#31125: 26; (emacs) `Highlight Interactively' Drew Adams
2018-04-12 11:38 ` Eli Zaretskii
2018-04-12 14:27 ` Drew Adams [this message]
[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=314419b3-b645-40de-b3cd-be34956a7247@default \
--to=drew.adams@oracle.com \
--cc=31125@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).