From: Drew Adams <drew.adams@oracle.com>
To: 15832@debbugs.gnu.org
Subject: bug#15832: 24.3.50; doc of `up-list' and moving by "parens"
Date: Thu, 7 Nov 2013 20:22:45 -0800 (PST) [thread overview]
Message-ID: <dbab4d15-023e-4402-b8d1-66f87b4d236d@default> (raw)
1. The doc strings of `up-list' and similar commands do not make clear
that the movement is not necessarily about parentheses (in spite of the
command names). As (emacs) `Moving by Parens' takes care to say, such
commands "move over groupings delimited by parentheses (or whatever else
serves as delimiters in the language you are working with)." The
information in parentheses in this phrase is what is missing from the
doc strings.
2. `up-list' should be added to the list of commands mentioned in
(emacs) `Moving by Parens'. `down-list' and `backward-up-list' are
mentioned, but not `up-list'.
Emacs Lisp is a big part of Emacs, yet the only place where `up-list' is
mentioned in the Emacs manual is in node `Tex Editing', where it is
described as "moving forward past the close brace." `Moving by Parens'
is a reasonable place to mention `up-list'.
3. (elisp) `List Motion' mentions that the syntax table controls which
characters are treated like parentheses, which is good. It then
cross-references (emacs) `Moving by Parens' "for user-level commands."
It is good to cross-reference, but what are described at (elisp) `List
Motion' *are* user-level commands, so the characterization "for
user-level commands" is confusing and misleading. The cross reference
should just say "see also".
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2013-10-19 on LEG570
Bzr revision: 114715 rgm@gnu.org-20131019023520-s8mwtib7xcx9e05w
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --enable-checking 'CFLAGS=-O0 -g3' CPPFLAGS=-DGLYPH_DEBUG=1'
next reply other threads:[~2013-11-08 4:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 4:22 Drew Adams [this message]
2014-02-10 5:49 ` bug#15832: 24.3.50; doc of `up-list' and moving by "parens" Lars Ingebrigtsen
2014-02-10 6:11 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dbab4d15-023e-4402-b8d1-66f87b4d236d@default \
--to=drew.adams@oracle.com \
--cc=15832@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 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.