GNU bug report logs - #49944
parse-partial-sexp fails to signal an error when (> START LIMIT).

Previous Next

Full log

Message #23 received at 49944 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: acm <at> muc.de, monnier <at> iro.umontreal.ca, 49944 <at> debbugs.gnu.org
Subject: Re: bug#49944: parse-partial-sexp fails to signal an error when (>
 START LIMIT).
Date: Tue, 10 Aug 2021 17:03:13 +0300

> From: Lars Ingebrigtsen <larsi <at> gnus.org>
> Date: Tue, 10 Aug 2021 15:50:49 +0200
> Cc: 49944 <at> debbugs.gnu.org, Stefan Monnier <monnier <at> iro.umontreal.ca>
> 
> Alan Mackenzie <acm <at> muc.de> writes:
> 
> > We definitely have a bug here.  The documentation in the elisp manual
> > says that the scanning is done "starting at START".  You're saying it's
> > perfectly OK to start scanning at "LIMIT"?  This violates the doc.
> 
> This is what all function like this say.  To take patient zero --
> narrow-to-region:
> 
> ---
> When calling from Lisp, pass two arguments START and END:
> positions (integers or markers) bounding the text that should
> remain visible.
> ---
> 
> Nothing here about allowing END to come before START, but it does allow
> that, and so do most (all?) similar commands.

Indeed, if the results are predictable, I see no reason not to support
START and END in any order, as we do in many places.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.