From: Juri Linkov <juri@jurta.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 7534@debbugs.gnu.org
Subject: bug#7534: 24.0.50; G-g within Isearch regexp mode
Date: Thu, 02 Dec 2010 22:31:48 +0000 [thread overview]
Message-ID: <878w0724dn.fsf@mail.jurta.org> (raw)
In-Reply-To: <AANLkTikXh3_HyAT3Q5-a8s7nXYkjbFG0ASg5GDmd21LJ@mail.gmail.com> (Dani Moncayo's message of "Thu, 2 Dec 2010 20:47:16 +0100")
> Recipe:
> 0) Start Emacs (-Q)
> 1) Place point at the beginning of the *scratch* buffer.
> 2) Search for the regexp "iss" (C-M-s iss) --> The last `s' is
> unmatched as expected, OK.
> 3) Type C-g --> The unmatched part disappears. Everything OK so far.
> 4) Now repeat steps #2 and #3 with the regexp "is[". --> This time C-g
> behaves differently. Instead of deleting the unmatched part, it ends
> Isearch mode.
>
> The fail seems to appear whenever `[' is the first character in the
> unmatched part. For instance:
> * C-M-s iss[ C-g --> Works as expected (unmatched part deleted).
> * C-M-s is[blablabla --> Doesn't work as expected (Isearch cancelled).
IMO, this is consistent behavior. As the message says after typing `['
it's incomplete input, so C-g behaves exactly like if there is no input
for `[' (and an unfinished sequence of characters that follows it).
So the main principle here is that "incomplete input" means "no input"
for Isearch, and given this rule all your examples work as expected, i.e.
"C-M-s is[ C-g" works like "C-M-s is C-g"
"C-M-s iss[ C-g" works like "C-M-s iss C-g"
"C-M-s is[blablabla C-g" works like "C-M-s is C-g"
next prev parent reply other threads:[~2010-12-02 22:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 19:47 bug#7534: 24.0.50; G-g within Isearch regexp mode Dani Moncayo
2010-12-02 22:31 ` Juri Linkov [this message]
2010-12-03 7:57 ` Dani Moncayo
2010-12-05 23:11 ` Juri Linkov
2010-12-06 10:41 ` Dani Moncayo
2010-12-25 2:47 ` Juri Linkov
2011-01-04 11:42 ` Dani Moncayo
2011-01-15 9:57 ` bug#7534: C-g in " Dani Moncayo
2011-01-15 15:51 ` Stefan Monnier
2011-01-16 1:06 ` Juri Linkov
2011-02-04 7:54 ` bug#7534: what about committing the patch also to emacs-23? Dani Moncayo
2011-02-04 14:40 ` Stefan Monnier
2011-02-04 15:39 ` Dani Moncayo
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=878w0724dn.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=7534@debbugs.gnu.org \
--cc=dmoncayo@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).