unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: xah lee <xah@xahlee.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: bug#1406: backward-up-list reports scan error incorrectly?
Date: Thu, 27 Nov 2008 12:19:51 +0000	[thread overview]
Message-ID: <20081127121951.GA3137@muc.de> (raw)
In-Reply-To: <20081122140446.GC3330@muc.de>

Hi, Xah!

> > though, isn't this something easy to fix?

> No, because it isn't a bug.  It's the way the function is meant to work.
> If there is a bug, it's that the doc-string (and maybe the elisp manual,
> I haven't looked) is vague and incomplete.

I've amended the Emacs manual (.../doc/emacs/programs.texi) and the doc
strings of `backward-up-list' and several similar functions
(.../lisp/emacs-lisp/lisp.el).

If you're interested, have a look at the changes in
<http://cvs.savannah.gnu.org/viewvc/emacs/?root=emacs>.

-- 
Alan Mackenzie (Nuremberg, Germany).




       reply	other threads:[~2008-11-27 12:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <EAA45A2E-4CC6-4F13-863A-9A934FF60165@xahlee.org>
     [not found] ` <20081121231944.GB2089@muc.de>
     [not found]   ` <5F3AB054-C158-4518-9C93-6938EB2D123D@xahlee.org>
     [not found]     ` <20081122123644.GA3330@muc.de>
     [not found]       ` <12CBE034-485F-49CE-9EF6-2C33A51AF0C1@xahlee.org>
     [not found]         ` <9331FB10-71C6-4B1B-94B6-B5C9B3667B74@xahlee.org>
     [not found]           ` <20081122140446.GC3330@muc.de>
2008-11-27 12:19             ` Alan Mackenzie [this message]
2008-11-27 15:56               ` bug#1406: backward-up-list reports scan error incorrectly? xah lee
2008-11-27 22:09                 ` Alan Mackenzie
2008-11-27 22:49                   ` xah lee
     [not found]             ` <mailman.1345.1227787599.26697.help-gnu-emacs@gnu.org>
2008-11-27 15:52               ` Xah Lee

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=20081127121951.GA3137@muc.de \
    --to=acm@muc.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=xah@xahlee.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.
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).