From: Juri Linkov <juri@jurta.org>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 9972@debbugs.gnu.org
Subject: bug#9972: 24.0.90; "C-s/C-r" from the minibuffer don't clear the current text
Date: Sun, 06 Nov 2011 19:01:36 +0200 [thread overview]
Message-ID: <87sjm1nq1b.fsf@mail.jurta.org> (raw)
In-Reply-To: <CAH8Pv0ifP87kKNJM5u8-STs_OsoJOYrzQb5-DXmV910j5QsULw@mail.gmail.com> (Dani Moncayo's message of "Sun, 6 Nov 2011 17:37:44 +0100")
>>> IMO, It isn't worth making C-s (and C-r, C-M-s, C-M-r) look up also in
>>> the current minibuffer text, because it is usually small enough not to
>>> need that (how often do you use that feature?).
>>
>> I use this feature all the time!
>
> For searching in the _current_ minibuffer text? How long are such text?
It doesn't matter how long it is.
Just imagine the minibuffer search as continuously searching backward
in a buffer with lines:
history3
history2
history1
history0
where "history0" is initial text in the minibuffer.
What you propose is to delete the line "history0" before running Isearch.
This makes no sense at all.
next prev parent reply other threads:[~2011-11-06 17:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-06 14:22 bug#9972: 24.0.90; "C-s/C-r" from the minibuffer don't clear the current text Dani Moncayo
2011-11-06 14:37 ` Juri Linkov
2011-11-06 14:47 ` Dani Moncayo
2011-11-06 15:10 ` Juri Linkov
2011-11-06 15:57 ` Dani Moncayo
2011-11-06 16:04 ` Dani Moncayo
2011-11-06 16:16 ` Juri Linkov
2011-11-06 16:37 ` Dani Moncayo
2011-11-06 17:01 ` Juri Linkov [this message]
2011-11-06 17:42 ` Dani Moncayo
2011-11-06 17:53 ` Dani Moncayo
2011-11-06 18:11 ` Drew Adams
2011-11-06 18:20 ` Juri Linkov
2011-11-06 19:07 ` Andreas Schwab
2011-11-09 15:27 ` Dani Moncayo
2011-11-09 16:17 ` Juri Linkov
2011-11-06 18:01 ` Drew Adams
2011-11-06 17:17 ` Drew Adams
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=87sjm1nq1b.fsf@mail.jurta.org \
--to=juri@jurta.org \
--cc=9972@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 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.