GNU bug report logs - #66406
Broken `re-search-forward' (?)

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#66406: closed (Broken `re-search-forward' (?))
Date: Mon, 09 Oct 2023 02:29:02 +0000

[Message part 1 (text/plain, inline)]

Your message dated Mon, 09 Oct 2023 05:28:00 +0300
with message-id <83zg0swmvj.fsf <at> gnu.org>
and subject line Re: bug#66406: Broken `re-search-forward' (?)
has caused the debbugs.gnu.org bug report #66406,
regarding Broken `re-search-forward' (?)
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
66406: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=66406
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Paul Pogonyshev <pogonyshev <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Broken `re-search-forward' (?)
Date: Sun, 8 Oct 2023 12:35:47 +0200

[Message part 3 (text/plain, inline)]

In a recent Emacs master (as provided in Silex's Docker image):

$ emacs --batch --eval "(with-temp-buffer (insert
\"\n;;;###autoload\n(defun ...)\n\") (goto-char 1) (print
(re-search-forward \"^[[:space:]]*;;;###autoload[[:space:]]*$\" nil t)))"

Prints nil.

With every stable version of Emacs I have this prints 16.

Paul

[Message part 4 (text/html, inline)]

[Message part 5 (message/rfc822, inline)]

From: Eli Zaretskii <eliz <at> gnu.org>
To: Paul Pogonyshev <pogonyshev <at> gmail.com>
Cc: contovob <at> tcd.ie, 66406-done <at> debbugs.gnu.org
Subject: Re: bug#66406: Broken `re-search-forward' (?)
Date: Mon, 09 Oct 2023 05:28:00 +0300

> Cc: 66406 <at> debbugs.gnu.org
> From: Paul Pogonyshev <pogonyshev <at> gmail.com>
> Date: Sun, 8 Oct 2023 22:06:23 +0200
> 
> > > In a recent Emacs master (as provided in Silex's Docker image):
> >
> > Any chance of knowing which commit precisely?
> 
> Not really, if you evaluate `emacs-repository-version' on Silex-image-packaged Emacs, result is nil.
> As far as I know, they are just built from Emacs VCS snapshot tarballs, but exact commit hash is lost
> in the build process.  This was even discussed before:
> https://github.com/Silex/docker-emacs/issues/86#issuecomment-1234266607 I don't know the
> details, but apparently GNU provides the snapshots ("archive tarballs are downloaded and
> unpacked"), so you could just inject revision number in the proper place and then get better bug
> reports. I'd provide commit number if I knew it somehow.
> 
> > I get 16 with today's master as well
> 
> Then it is apparently fixed already.

I also get 16, so I presume this bug was already fixed, and I'm
closing it.

Previous Next

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