unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Mon, 14 Mar 2016 01:40:55 +0200	[thread overview]
Message-ID: <87ziu22bg8.fsf@mail.linkov.net> (raw)
In-Reply-To: <95c9a103-69cb-4500-bc87-7aec290caf7c@default> (Drew Adams's message of "Sat, 12 Mar 2016 15:11:59 -0800 (PST)")

> In the meantime, I suggest we anyway provide complete such
> information on a help key.  This "solution" can remain,
> regardless of whatother designs might be adopted to provide
> some such info all of the time (instead of just on demand).

You mean displaying this information in the *Help* buffer
like ‘?’ in query-replace does?

> Wrt this bug and the prompt, for now: Either drop any
> indication of state in the prompt (which might confuse
> people) or show only what we showed before (regexp vs
> literal), ignoring indicating char folding, case folding,
> and whitespace folding.

Right, let's keep the status quo for now, and display
only regexp-function statuses in the prompt.





  reply	other threads:[~2016-03-13 23: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
2016-03-12 23:11                       ` Drew Adams
2016-03-13 23:40                         ` Juri Linkov [this message]
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=87ziu22bg8.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).