unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 15832@debbugs.gnu.org
Subject: bug#15832: 24.3.50; doc of `up-list' and moving by "parens"
Date: Sun, 09 Feb 2014 21:49:44 -0800	[thread overview]
Message-ID: <87lhxj7c07.fsf@building.gnus.org> (raw)
In-Reply-To: <dbab4d15-023e-4402-b8d1-66f87b4d236d@default> (Drew Adams's message of "Thu, 7 Nov 2013 20:22:45 -0800 (PST)")

Drew Adams <drew.adams@oracle.com> writes:

> 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.

Fixed on trunk.

> 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'.

`up-list' doesn't have a keyboard definition, which is why it's probably
not documented in the Emacs manual.

> 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".

The things described in the Emacs manual here are clearly more
user-levelish, so I think that's OK.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  reply	other threads:[~2014-02-10  5:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08  4:22 bug#15832: 24.3.50; doc of `up-list' and moving by "parens" Drew Adams
2014-02-10  5:49 ` Lars Ingebrigtsen [this message]
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

  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=87lhxj7c07.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --cc=15832@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).