unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dani Moncayo <dmoncayo@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 14729@debbugs.gnu.org
Subject: bug#14729: 24.3.50; Isearch oddity
Date: Sat, 29 Jun 2013 19:22:37 +0200	[thread overview]
Message-ID: <CAH8Pv0j2i_x9UsJAjxXgDoazDZ_GqeSvX4U+3d1+KXHR7PRH=A@mail.gmail.com> (raw)
In-Reply-To: <87mwqbay6p.fsf@mail.jurta.org>

On Fri, Jun 28, 2013 at 1:44 AM, Juri Linkov <juri@jurta.org> wrote:
>> Recipe from "emacs -Q":
>>   M-< b u f C-s C-s f e r
>
> I guess this key sequence should be rather:
>
>     M-< C-s b u f C-s C-s f e r
>
> Is this what you meant?

Yes, of course.  Silly mistake on my part.

>> After that, the echo area indicates that, in the current Isearch, I'm
>> looking for "buffer", and I've found the "buf" part, but not the
>> remaining "fer".
>>
>> That makes no sense, because that cannot happen in the current buffer,
>> where every instance of "buf" is followed by a "fer".
>
> This is an interesting state of the search.  The search is failed,
> so it assumes that adding more characters to the failed search should
> leave the search in the failed state.  Isn't this logically correct?

Of course it is correct.  If there is not match for FOO, obviously
there will be no match for FOOBAR.

> What do you expect it to do in this case?

I expect that the fontification of the echo area reflects what is
happening: that the whole search string ("buffer") is unmatched (not
only the last "fer"), since the current search begins just after the
last instance of "buf" in the buffer [1], and there is no match
(neither full nor partial) of the current search string between that
location and the end of the buffer.


------------
[1] Think of "C-s" within an Isearch session as "repeat the current
search, but starting at the current point location".

--
Dani Moncayo





  reply	other threads:[~2013-06-29 17:22 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27  9:58 bug#14729: 24.3.50; Isearch oddity Dani Moncayo
2013-06-27 23:44 ` Juri Linkov
2013-06-29 17:22   ` Dani Moncayo [this message]
2013-06-29 21:53     ` Juri Linkov
2013-06-29 22:34       ` Dani Moncayo
2013-06-30  3:11         ` Drew Adams
2021-12-04  3:51       ` Lars Ingebrigtsen
2021-12-04 16:48         ` bug#14729: [External] : " Drew Adams
2021-12-04 19:59         ` Juri Linkov
2021-12-04 22:06           ` Lars Ingebrigtsen
2021-12-05  9:35             ` Juri Linkov
2021-12-05 20:22               ` Lars Ingebrigtsen
2021-12-06  2:09                 ` bug#14729: [External] : " Drew Adams
2021-12-06  9:33                   ` Juri Linkov
2021-12-06  9:40                     ` Lars Ingebrigtsen
2021-12-06 16:01                     ` Drew Adams
2021-12-06 17:03             ` Juri Linkov
2021-12-07 20:48               ` Lars Ingebrigtsen
2021-12-07 21:53                 ` Juri Linkov

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='CAH8Pv0j2i_x9UsJAjxXgDoazDZ_GqeSvX4U+3d1+KXHR7PRH=A@mail.gmail.com' \
    --to=dmoncayo@gmail.com \
    --cc=14729@debbugs.gnu.org \
    --cc=juri@jurta.org \
    /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).