all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Dima Kogan <dima-8Bn8oVo35dduSJGsrdOfxA@public.gmane.org>
Cc: 21208-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org
Subject: bug#21208: 25.0.50; isearch gets confused with 'too many words'
Date: Fri, 07 Aug 2015 22:40:31 +0200	[thread overview]
Message-ID: <86fv3u4ytc.fsf@example.com> (raw)
In-Reply-To: <mailman.7939.1438961528.904.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org> (Dima Kogan's message of "Fri, 07 Aug 2015 03:27:48 -0700")

Dima Kogan <dima-8Bn8oVo35dduSJGsrdOfxA@public.gmane.org> writes:
> Hi. I'm running a very recent build of emacs from git:
>
>   https://github.com/emacs-mirror/emacs/commit/0aec2aaccd8b745fa7214f3edd453c04a04bfba4
>
> I just found another isearch regression. Recipe:
>
> 1. emacs -Q
>
> 2. Create or open file such that the buffer contains
> -------------------------
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
>
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234 1234
> -------------------------
> i.e two identical long lines containing lots of words '1234'.
>
> 3. Point to start of buffer
>
> 4. C-s
>
> 5. C-w multiple times. As you press C-w, you grow the string being
> sought; you can see the match highlighted on the line being selected and
> on the next line
>
> 4. Eventually (column 239 or so) the minibuffer says 'too many words',
> and the search no longer matches anything on either line. The sought
> string looks like it's appending words without spaces ("123412341234"
> instead of "1234 1234 1234"). Manually fixing that with M-e doesn't
> appear to help.

Confirmed -- was about to report it as well!

Best regards,
  Seb





       reply	other threads:[~2015-08-07 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.7939.1438961528.904.bug-gnu-emacs@gnu.org>
     [not found] ` <mailman.7939.1438961528.904.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2015-08-07 20:40   ` Sebastien Vauban [this message]
2015-08-07 10:27 bug#21208: 25.0.50; isearch gets confused with 'too many words' Dima Kogan
2015-09-03 22:27 ` Juri Linkov
2016-06-11  2:34 ` Noam Postavsky

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86fv3u4ytc.fsf@example.com \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=21208-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org \
    --cc=dima-8Bn8oVo35dduSJGsrdOfxA@public.gmane.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.