From: Juri Linkov <juri@jurta.org>
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: Mon, 22 Aug 2011 14:06:18 +0300 [thread overview]
Message-ID: <8739gtg0wp.fsf@mail.jurta.org> (raw)
In-Reply-To: <CAH8Pv0iiAYFwWTLBTjTqKQiXS56RbmcXKdjrJ0MKGzURUSdmEw@mail.gmail.com> (Dani Moncayo's message of "Sun, 21 Aug 2011 21:24:41 +0200")
> If that is the resulting behavior, it is indeed a problem, but a small
> one IMO. Since `C-s C-s' retrieves the first entry from the search
> ring, `M-p' should retrieve the _previous_ one, i.e., the second.
This complicates the behavior of `M-p'.
Do you propose the following logic?
1. When the user starts Isearch with `C-s', then
`M-p' should retrieve the _first_ entry from the search ring.
2. But when the user starts Isearch with `C-s C-s', then
`M-p' should retrieve the _second_ entry from the search ring.
But what to do when the user starts Isearch with `C-s C-s', but
changes his mind and deletes it from the current search string,
i.e. types `C-s C-s DEL'. What should `M-p' bring in this case?
The first or the second entry?
next prev parent reply other threads:[~2011-08-22 11:06 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
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 [this message]
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=8739gtg0wp.fsf@mail.jurta.org \
--to=juri@jurta.org \
--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).