From: Juri Linkov <juri@jurta.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 10113@debbugs.gnu.org
Subject: bug#10113: 24.0.91; Isearch & `M-e'
Date: Wed, 23 Nov 2011 01:21:33 +0200 [thread overview]
Message-ID: <871uszwxoi.fsf@mail.jurta.org> (raw)
In-Reply-To: <CAH8Pv0hoDrR8Zh-uWFWS3yMKJGfNv7O7guz4K01pd_LEA=gFTA@mail.gmail.com> (Dani Moncayo's message of "Tue, 22 Nov 2011 23:44:54 +0100")
> Here are two recipes (from emacs -Q) that seem to be bugs in Isearch:
Thanks for recipes.
> --------------------------------------------
> First case:
> 1. Write the text "buffer buffeR".
> 2. Type "C-a C-s b u f f e R M-e DEL RET".
> --> Here the _current_ match should be the first "buffe", but it's the
> second one.
Why do think Isearch should go back to the first match without the user
typing `C-r C-r' explicitly?
> --------------------------------------------
> Second case:
> 1. Write the text "buffer buffeR".
> 2. Type "C-a C-s b u f f e R M-e DEL r RET".
> --> Here both words should be matched, but only the first one is.
Actually this is unrelated to `isearch-edit-string'.
The first time you type an upper-case letter,
Isearch switches to case-sensitive mode.
You can observe this effect with the following case:
1. Write the text "buffer buffeR buffeRr buffeRR".
2. Type "C-a C-s b u f f e R r M-c".
After you type the first upper-case letter `R', Isearch switches
to case-sensitive mode, and after typing the next lower-case `r'
Isearch doesn't match "buffeRR". It does that only when you
switch back to case-insensitive search mode by typing `M-c'.
next prev parent reply other threads:[~2011-11-22 23:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 22:44 bug#10113: 24.0.91; Isearch & `M-e' Dani Moncayo
2011-11-22 23:21 ` Juri Linkov [this message]
2011-11-23 8:02 ` Dani Moncayo
2011-11-23 14:30 ` Stefan Monnier
2011-11-23 14:56 ` Dani Moncayo
2011-11-23 19:54 ` Stefan Monnier
2011-11-23 21:14 ` Dani Moncayo
2011-11-23 20:20 ` Juri Linkov
2011-11-23 20:59 ` Dani Moncayo
2011-11-23 21:23 ` Juri Linkov
2011-12-01 19:41 ` Stefan Monnier
2011-12-04 18:14 ` Johan Bockgård
2011-12-05 10:49 ` Juri Linkov
2011-12-05 17:19 ` Richard Stallman
2022-03-21 21:52 ` Lars Ingebrigtsen
2022-03-22 8:47 ` Juri Linkov
2022-03-22 14:12 ` Lars Ingebrigtsen
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=871uszwxoi.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=10113@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).