From: Juri Linkov <juri@linkov.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: michael_heerdegen@web.de, 22991@debbugs.gnu.org,
bruce.connor.am@gmail.com, Kaushal Modi <kaushal.modi@gmail.com>
Subject: bug#22991: 25.0.92: C-u C-s does not display "Regexp I-search:" in the echo area
Date: Sun, 13 Mar 2016 00:40:32 +0200 [thread overview]
Message-ID: <87twkbwbwf.fsf@mail.linkov.net> (raw)
In-Reply-To: <a0ddfcf3-38c0-4cfd-a2c3-979dbc92a447@default> (Drew Adams's message of "Sat, 12 Mar 2016 07:14:28 -0800 (PST)")
> 1. I agree with Michael in this case. The prompt should
> faithfully reflect the current search state/mode - until we
> find a better way to convey that information. In any case,
> the prompt should not mislead by reflecting a different
> search behavior from what is current.
Reflecting all current search states might produce overly long
default prompts as
Character-folding case-folding whitespace-folding I-search:
>> 4. All of that said, I think that we really need to find
>> some _other way than the prompt_ to indicate, completely,
>> the search state. And then the prompt can perhaps just be
>> something like "Isearch" in all cases. The prompt is not
>> adequate for conveying just what the current search state is.
>
> Something that I think should be available, starting now, is
> an Isearch key binding that describes the current search state
> _completely_, much as `C-u C-x =' describes the char at point.
>
> This state information should be on prefix key `C-h'. It
> could be on a new key on that prefix or it could simply be
> added to `isearch-describe-mode' - the key could be `C-h m'.
Or an option/state (say, ‘isearch-message-verbose’) toggleable
with ‘isearch-toggle-message-verbose’ like other states
(e.g. ‘isearch-toggle-case-fold’) that will toggle between
displaying full/brief state description in the prompt.
next prev parent reply other threads:[~2016-03-12 22:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 19:48 bug#22991: 25.0.92: C-u C-s does not display "Regexp I-search:" in the echo area Kaushal Modi
2016-03-11 20:46 ` Kaushal Modi
2016-03-11 20:54 ` Eli Zaretskii
2016-03-11 20:58 ` Kaushal Modi
2016-03-11 21:08 ` Eli Zaretskii
2016-03-11 21:22 ` Kaushal Modi
2016-03-11 22:22 ` Artur Malabarba
2016-03-11 22:36 ` Kaushal Modi
2016-03-11 23:37 ` Michael Heerdegen
2016-03-11 23:40 ` Kaushal Modi
2016-03-12 1:11 ` Artur Malabarba
2016-03-12 4:56 ` Kaushal Modi
2016-03-12 7:49 ` Eli Zaretskii
2016-03-12 12:33 ` Michael Heerdegen
2016-03-12 12:46 ` Eli Zaretskii
2016-03-12 12:51 ` Michael Heerdegen
2016-03-12 13:52 ` Artur Malabarba
2016-03-12 14:35 ` Kaushal Modi
2016-03-12 16:13 ` Eli Zaretskii
[not found] ` <<83h9gcgmor.fsf@gnu.org>
2016-03-12 15:14 ` Drew Adams
2016-03-12 16:25 ` Drew Adams
2016-03-12 22:40 ` Juri Linkov [this message]
2016-03-12 23:11 ` Drew Adams
2016-03-13 23:40 ` Juri Linkov
2016-03-14 0:03 ` Drew Adams
2016-03-14 3:39 ` Eli Zaretskii
2016-03-14 13:50 ` Kaushal Modi
2016-03-14 15:29 ` Drew Adams
2016-03-14 16:29 ` Artur Malabarba
2016-03-14 18:17 ` Eli Zaretskii
2016-03-14 18:32 ` Kaushal Modi
2016-03-12 7:30 ` Eli Zaretskii
2016-03-12 7:29 ` Eli Zaretskii
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=87twkbwbwf.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=22991@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=drew.adams@oracle.com \
--cc=kaushal.modi@gmail.com \
--cc=michael_heerdegen@web.de \
/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).