unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: 10634@debbugs.gnu.org
Subject: bug#10634: `forward-list' scan error
Date: Mon, 23 Aug 2021 17:16:25 +0200	[thread overview]
Message-ID: <87y28sp4xi.fsf@gnus.org> (raw)
In-Reply-To: <87lh7ed73g.fsf@mbork.pl> (Marcin Borkowski's message of "Sun, 24 Jan 2016 22:02:11 +0100")

Marcin Borkowski <mbork@mbork.pl> writes:

> On 2012-01-28, at 23:20, Raffaele Ricciardi <rfflrccrd@gmail.com> wrote:
>
>> Error: "forward-list: Scan error: "Containing expression ends
>> prematurely", 336, 336"
>>
>> How to reproduce it:
>> - emacs -Q
>> - switch to *scratch*
>> - in the following code:
>>
>> (abc (def) (ghi) lmn)
>>
>> `forward-list' fails in different positions, for instance (| is point):
>>
>> (abc (|d|e|f|) (ghi) lmn)
>>
>> Software: GNU Emacs 23.3.1 (i686-pc-linux-gnu, GTK+ Version 2.20.1) of
>> 2011-12-10 on debian
>
> Hi all,
>
> while I can easily reproduce this on current Emacs (25.1.50.1), I'm not
> sure whether this is really a bug.  (Maybe it is a bug in the
> docstring?)

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

This has changed a bit since reported a decade ago.  The command now says:

user-error: No next group

Which is the correct thing here -- the command is (now) documented to
"Move forward across one balanced group of parentheses.", and in the
case here, there's no group of parentheses to move forward over.

So this works as intended (`up-list' is the command to use in this
instance, most likely), and I'm closing this bug report.

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





      parent reply	other threads:[~2021-08-23 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-28 23:20 bug#10634: `forward-list' scan error Raffaele Ricciardi
2016-01-24 21:02 ` Marcin Borkowski
2016-01-25 17:05   ` Eli Zaretskii
2021-08-23 15:16   ` Lars Ingebrigtsen [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

  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=87y28sp4xi.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=10634@debbugs.gnu.org \
    --cc=mbork@mbork.pl \
    /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).