From: Eli Zaretskii <eliz@gnu.org>
To: Paul Pogonyshev <pogonyshev@gmail.com>
Cc: contovob@tcd.ie, 66406-done@debbugs.gnu.org
Subject: bug#66406: Broken `re-search-forward' (?)
Date: Mon, 09 Oct 2023 05:28:00 +0300 [thread overview]
Message-ID: <83zg0swmvj.fsf@gnu.org> (raw)
In-Reply-To: <CAG7BparNRKQuqeca5ZwAX2AX8gBn+vH5mwPJrxTBqryH2Hbc8g@mail.gmail.com> (message from Paul Pogonyshev on Sun, 8 Oct 2023 22:06:23 +0200)
> Cc: 66406@debbugs.gnu.org
> From: Paul Pogonyshev <pogonyshev@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.
next prev parent reply other threads:[~2023-10-09 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 10:35 bug#66406: Broken `re-search-forward' (?) Paul Pogonyshev
2023-10-08 11:41 ` Eli Zaretskii
2023-10-08 19:39 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-10-08 20:06 ` Paul Pogonyshev
2023-10-09 2:28 ` Eli Zaretskii [this message]
2023-10-10 13:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83zg0swmvj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=66406-done@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=pogonyshev@gmail.com \
/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).