From: Dani Moncayo <dmoncayo@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 9972-done@debbugs.gnu.org
Subject: bug#9972: 24.0.90; "C-s/C-r" from the minibuffer don't clear the current text
Date: Sun, 6 Nov 2011 18:53:23 +0100 [thread overview]
Message-ID: <CAH8Pv0jtcYDRLu=uyAmL2Lh1ZRfs7yD+v+Gk0EW6F4y9ftUeyA@mail.gmail.com> (raw)
In-Reply-To: <CAH8Pv0j2bwuNEKLs-2N_UTtGoG3-qVU3DXZcQUisKnrZVK75Og@mail.gmail.com>
> Like you (and Drew, and I guess everyone in this list), I like
> consistency and generality.
>
> Actually, what I don't like in the current behavior of C-s (and the
> other 3) when invoked from the minibuffer is the fact that the current
> minibuffer text remains there after hitting C-s (like if I were typed
> it, but even being read-only!). That scenario is not like users are
> used to when the type `C-s'. They expect to see a clean minibuffer
> prompt "I-search: ", with the cursor after it.
>
> So, what about making the Isearch commands start that way, but
> considering the current minibuffer text (the one present before C-s
> was invoked) as the first entry for the search, as you pointed out?
Forget about this. I now realize what you and Drew meant, and I agree with you.
I'm closing this bug report, and sorry for wasting your time.
--
Dani Moncayo
next prev parent reply other threads:[~2011-11-06 17:53 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
2011-11-06 17:42 ` Dani Moncayo
2011-11-06 17:53 ` Dani Moncayo [this message]
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='CAH8Pv0jtcYDRLu=uyAmL2Lh1ZRfs7yD+v+Gk0EW6F4y9ftUeyA@mail.gmail.com' \
--to=dmoncayo@gmail.com \
--cc=9972-done@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 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.