From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Juri Linkov <juri@jurta.org>
Cc: "10148@debbugs.gnu.org" <10148@debbugs.gnu.org>,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#10148: 24.0.91; "pending" regexp Isearch
Date: Sun, 17 Apr 2022 17:12:03 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488FD8112CEA7D92519F283F3F09@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87bkwzao8q.fsf@gnus.org>
Could someone please answer the question
I posed in message #50?
Question: How does this relate to the Isearch
error messages that indicate invalid and
incomplete regexp patterns, and are thus more
specific: "\\`Premature \\|\\`Unmatched \\|\\`Invalid "?
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=10148#50
next prev parent reply other threads:[~2022-04-17 17:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-27 12:52 bug#10148: 24.0.91; "pending" regexp Isearch Dani Moncayo
2011-11-29 0:39 ` Juri Linkov
2011-11-29 10:26 ` Dani Moncayo
2011-11-30 9:51 ` Juri Linkov
2011-11-30 10:26 ` Dani Moncayo
2011-11-30 10:38 ` Juri Linkov
2011-11-30 10:55 ` Dani Moncayo
2011-11-30 11:04 ` Dani Moncayo
2011-11-30 14:08 ` Stefan Monnier
2011-11-30 14:21 ` Dani Moncayo
2011-11-30 14:47 ` Drew Adams
2011-11-30 15:35 ` Juri Linkov
2011-11-30 19:13 ` Stefan Monnier
2011-12-01 7:37 ` Juri Linkov
2011-12-01 11:34 ` Eli Zaretskii
2011-12-01 15:22 ` Drew Adams
2011-12-01 16:06 ` Stefan Monnier
2022-04-17 12:27 ` Lars Ingebrigtsen
2022-04-17 17:12 ` Drew Adams [this message]
2022-04-18 19:09 ` Juri Linkov
2022-04-18 19:20 ` Drew Adams
2022-04-18 19:07 ` Juri Linkov
2022-04-18 19:19 ` Lars Ingebrigtsen
2022-04-20 7:34 ` Juri Linkov
2022-04-20 10:52 ` Lars Ingebrigtsen
2022-04-20 17:13 ` Juri Linkov
2022-04-21 11:34 ` Lars Ingebrigtsen
2022-04-21 12:25 ` 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=SJ0PR10MB5488FD8112CEA7D92519F283F3F09@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=10148@debbugs.gnu.org \
--cc=juri@jurta.org \
--cc=larsi@gnus.org \
--cc=monnier@IRO.UMontreal.CA \
/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).