unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	"23010@debbugs.gnu.org" <23010@debbugs.gnu.org>
Subject: bug#23010: 25.1.50; Isearch help key to indicate current search state/mode
Date: Fri, 13 May 2022 21:05:14 +0000	[thread overview]
Message-ID: <SJ0PR10MB548889DB44A4AC4E8DB55C84F3CA9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <865ym9z7nk.fsf@mail.linkov.net>

> > I've also made other suggestions elsewhere, regarding
> > showing more such state in the mode-line.  And I do
> > that in isearch+.el.  E.g., mode-line lighter tells
> > you whether case-sensitive and whether regexp searching:
> >
> > (if case-fold-search
> >     (if isearch-regexp " R*SEARCH" " ISEARCH")
> >   (if isearch-regexp " R*search" " Isearch"))
> 
> I guess R means Regexp search.  But what does the asterisk
> after R mean?  On the mode line it usually indicates the
> modified buffer.

R*search and R*SEARCH are just meant to indicate a
regexp pattern (the former indicating case-sensitive).

The Isearch+ doc says what it means.  But I don't say
you need to follow what I did exactly.

The point was just to say that with very little screen
real estate (a mode-line lighter) we can show, and
dynamically update, a fair amount of info about the
current Isearch state: whether case-insensitive, and
whether regexp searching.

I intend it only as food for thought.





  reply	other threads:[~2022-05-13 21:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 15:28 bug#23010: 25.1.50; Isearch help key to indicate current search state/mode Drew Adams
2022-05-12 16:27 ` Lars Ingebrigtsen
2022-05-12 16:34   ` Drew Adams
2022-05-12 17:30     ` Juri Linkov
2022-05-12 17:43       ` Drew Adams
2022-05-13 17:03         ` Juri Linkov
2022-05-13 21:05           ` Drew Adams [this message]
2022-06-13 12:48   ` Lars Ingebrigtsen

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=SJ0PR10MB548889DB44A4AC4E8DB55C84F3CA9@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=23010@debbugs.gnu.org \
    --cc=juri@linkov.net \
    --cc=larsi@gnus.org \
    /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).