From: Drew Adams <drew.adams@oracle.com>
To: 31125@debbugs.gnu.org
Subject: bug#31125: 26; (emacs) `Highlight Interactively'
Date: Wed, 11 Apr 2018 07:45:54 -0700 (PDT) [thread overview]
Message-ID: <57ad2ae3-cfe5-4fca-a503-e106658d3e38@default> (raw)
In the Emacs manual, `i symbol TAB' shows `Highlight Interactively' as a
place where symbols are mentioned. They are, via
`highlight-symbol-at-point'. This perhaps the only place in the Emacs
manual where symbols are mentioned.
1. It seems (?), by tracking backward through `highlight-symbol-at-point'
and then (thing-at-point 'symbol), that `highlight-symbol-at-point' is
about highlighting Lisp symbols, not text that has characters with
symbol-constituent syntax. If so, it would be helpful for the doc of
`highlight-symbol*' to specifically say "Lisp symbol".
2. Assuming that it is in fact about Lisp symbols, please consider
adding a link in (emacs) `Highlight Interactively' to (elisp) `Symbols',
so readers of the Emacs manual can more easily discover something about
Lisp symbols.
In GNU Emacs 26.1 (build 1, x86_64-w64-mingw32)
of 2018-04-10
Repository revision: c267421647510319d2a70554e42f0d1c394dba0a
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install 'CFLAGS=-O2 -static -g3''
next reply other threads:[~2018-04-11 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-11 14:45 Drew Adams [this message]
2018-04-11 16:49 ` bug#31125: 26; (emacs) `Highlight Interactively' Eli Zaretskii
[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
[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
2018-04-12 11:38 ` Eli Zaretskii
2018-04-12 14:27 ` Drew Adams
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=57ad2ae3-cfe5-4fca-a503-e106658d3e38@default \
--to=drew.adams@oracle.com \
--cc=31125@debbugs.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).