all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 15832@debbugs.gnu.org
Subject: bug#15832: 24.3.50; doc of `up-list' and moving by "parens"
Date: Sun, 9 Feb 2014 22:11:42 -0800 (PST)	[thread overview]
Message-ID: <1059c795-dd53-41f9-95cb-fadf04df4008@default> (raw)
In-Reply-To: <87lhxj7c07.fsf@building.gnus.org>

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

It should still be mentioned.

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

If you want to say "for information about OTHER user-level
commands" or "for more information about these user-level
commands" (depending on which is meant), that would be fine, but
as it stands now it is confusing and misleading, giving
the impression that what are described here might NOT be
user-level commands.





      reply	other threads:[~2014-02-10  6:11 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
2014-02-10  6:11   ` Drew Adams [this message]

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=1059c795-dd53-41f9-95cb-fadf04df4008@default \
    --to=drew.adams@oracle.com \
    --cc=15832@debbugs.gnu.org \
    --cc=larsi@gnus.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.