unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 8861@debbugs.gnu.org, Dani Moncayo <dmoncayo@gmail.com>
Subject: bug#8861: 24.0.50; Isearch: Repeating the last search
Date: Thu, 27 Jan 2022 20:15:05 +0200	[thread overview]
Message-ID: <86a6fh6o5y.fsf@mail.linkov.net> (raw)
In-Reply-To: <87y231jbvl.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 27 Jan 2022 19:02:06 +0100")

>> When trying this, it seems it's worse than the default behavior because
>> treating the search string char by char is useful only when you are
>> typing it because highlighting the failed part helps to correct typos.
>> But when you want to search for the previous search string by `C-s C-s'
>> or by copy&paste from the clipboard/kill-ring it's more useful
>> to treat it as a whole.  For instance, often it's necessary to
>> put a string into the search ring (`C-s string RET') and search
>> its exact occurrence in another buffer (`C-x o C-s C-s').
>> It would be annoying when searching for e.g. "caterpillar"
>> will stop at "cat" and highlight it.
>
> Yes, it would be pretty odd...
>
>> However, your idea is not completely useless.  Currently isearch mode
>> is interactively incremental but you propose to extend it it into
>> non-interactively incremental (i.e. incremental even when the search
>> string is not composed interactively).  Maybe a new option/mode
>> could do that but I think it should not be enabled by default.
>
> ... and in my opinion, I don't think such a would find much use, so I'm
> closing this issue as "wontfix".

Please close also bug#14729 for the same reason, these two requests
are about the same fuzzy oddities with no clear solution.





  reply	other threads:[~2022-01-27 18:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 12:32 bug#8861: 24.0.50; Isearch: Repeating the last search Dani Moncayo
2011-06-14 13:11 ` Drew Adams
2011-06-14 13:52   ` Dani Moncayo
2011-06-14 15:20     ` Drew Adams
2011-06-14 17:33     ` Juri Linkov
2011-06-14 18:41       ` Dani Moncayo
2011-06-15  3:11         ` Stefan Monnier
2022-01-27 18:02       ` Lars Ingebrigtsen
2022-01-27 18:15         ` Juri Linkov [this message]
2022-01-27 18:58           ` 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=86a6fh6o5y.fsf@mail.linkov.net \
    --to=juri@jurta.org \
    --cc=8861@debbugs.gnu.org \
    --cc=dmoncayo@gmail.com \
    --cc=larsi@gnus.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).