From: Deniz Dogan <deniz@dogan.se>
To: Dani Moncayo <dmoncayo@gmail.com>
Cc: 9185@debbugs.gnu.org
Subject: bug#9185: 24.0.50; "C-s M-p" does not bring the tip of the search ring
Date: Thu, 28 Jul 2011 11:11:22 +0200 [thread overview]
Message-ID: <4E3127BA.30200@dogan.se> (raw)
In-Reply-To: <CAH8Pv0jQj8cmT5Ynz1FGfwxAho+jA+B=-qTd+0wnoRf+LyeEow@mail.gmail.com>
On 2011-07-28 11:08, Dani Moncayo wrote:
> On Thu, Jul 28, 2011 at 10:50, Deniz Dogan<deniz@dogan.se> wrote:
>>
>> C-s C-s immediately searches for the latest entry in the ring. If C-s M-p
>> did that too, things would be...weird. At least to me. I wouldn't really
>> mind that much if M-p brings back the latest entry but _doesn't_ perform the
>> actual search,
>
> You are forgetting to add<RET> after "C-s M-p". I see no weirdness
> here at all. It feel totally natural to me:
> * C-s start Isearch.
> * M-p brings the *last* ring entry (not the second one, as does now).
> *<RET> accepts the selected entry.
>
You never said to hit RET, that's why I was confused.
>> but it just feels kind of unnecessary since if you wanted to
>> search for that you could just C-s C-s to begin with.
>
> "C-s C-s" is the quick way of repeating the last search, but, as I
> explained in the OP, it doesn't allow you to check the search string
> before starting the search.
>
>
> Again: The fact that M-p brings the second entry from the ring
> (instead of the first one) seems annoying and counter-intuitive to me.
> It doesn't allow me to check the tip of the search ring before using
> it.
>
That's true. I'm with you on this one, but since this behavior is so
old, I wouldn't count on it changing any time soon.
Deniz
next prev parent reply other threads:[~2011-07-28 9:11 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 8:12 bug#9185: 24.0.50; "C-s M-p" does not bring the tip of the search ring Dani Moncayo
2011-07-28 8:18 ` Dani Moncayo
2011-07-28 8:20 ` Deniz Dogan
2011-07-28 8:43 ` Dani Moncayo
2011-07-28 8:50 ` Deniz Dogan
2011-07-28 9:08 ` Dani Moncayo
2011-07-28 9:11 ` Deniz Dogan [this message]
2011-07-28 9:17 ` Dani Moncayo
2011-07-28 9:11 ` Andreas Schwab
2011-07-28 9:29 ` Juri Linkov
2011-07-28 9:50 ` Juri Linkov
2011-07-28 10:05 ` Dani Moncayo
2011-07-28 11:13 ` Andreas Schwab
2011-07-28 11:32 ` Dani Moncayo
2011-07-28 11:44 ` Juri Linkov
2011-07-30 8:52 ` Juri Linkov
2011-08-10 19:03 ` Dani Moncayo
2011-08-13 15:24 ` Stefan Monnier
2011-08-14 11:14 ` Dani Moncayo
2011-08-14 12:36 ` Stefan Monnier
2011-08-14 14:47 ` Dani Moncayo
2011-08-21 17:56 ` Dani Moncayo
2011-08-21 18:35 ` Juri Linkov
2011-08-21 19:24 ` Dani Moncayo
2011-08-22 11:06 ` Juri Linkov
2011-08-22 12:09 ` Dani Moncayo
2011-08-22 21:34 ` Stefan Monnier
2011-08-23 9:52 ` Juri Linkov
2011-08-23 18:40 ` Stefan Monnier
2011-08-24 9:41 ` Juri Linkov
2011-08-24 14:23 ` Dani Moncayo
2011-08-24 15:44 ` Juri Linkov
2011-08-24 16:18 ` Dani Moncayo
2011-08-24 18:28 ` Juri Linkov
2011-08-24 23:21 ` Dani Moncayo
2011-08-24 23:54 ` Dani Moncayo
2011-08-25 9:01 ` Juri Linkov
2011-08-25 10:10 ` Dani Moncayo
2011-11-19 19:59 ` 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=4E3127BA.30200@dogan.se \
--to=deniz@dogan.se \
--cc=9185@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 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).