From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 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: Sat, 12 Mar 2016 13:33:09 +0100 [thread overview]
Message-ID: <87pouzzxiy.fsf@web.de> (raw)
In-Reply-To: <83h9gcgmor.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 12 Mar 2016 09:49:56 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> Second, I don't agree with Michael, so if we want to allow such a
> different behavior, I will insist on a user option.
I mean especially, if I end up with the default mode and the literal
search mode both show the same prompt, that would not be good. But yes,
what I really would like would be to always show the searching mode in
the prompt. This is not what you want, obviously.
Would it make sense to you to decide what to show in the prompt based on
the fact whether `search-default-mode' has a buffer local binding -
instead of introducing a new option (which seems a bit of overkill to
me)? I.e., if there is a buffer local binding that differs from the
global value, do what I want - else, do what you prefer.
Michael.
next prev parent reply other threads:[~2016-03-12 12:33 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 [this message]
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
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=87pouzzxiy.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=22991@debbugs.gnu.org \
--cc=bruce.connor.am@gmail.com \
--cc=eliz@gnu.org \
--cc=kaushal.modi@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).