all messages for Emacs-related lists mirrored at yhetil.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: Thu, 12 May 2022 17:43:03 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488A6CC22DD05739EF95A80F3CB9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <86zgjmd5g4.fsf@mail.linkov.net>

> So do you suggest something like what query-replace does
> where typing `?' displays help about replacements?
> Such a buffer could have a different name, e.g.
> " *Isearch status*" and display the values
> of all togglable options.

Please read the bug report.  I made several suggestions
in this regard.  But yes, what you ask was included in
the suggestions.
___

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"))

But adding char-folding and other state would be
unmanageable with just a lighter.  I don't suggest
trying to make the lighter communicate more - the
result would be more confusing than helpful.





  reply	other threads:[~2022-05-12 17:43 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 [this message]
2022-05-13 17:03         ` Juri Linkov
2022-05-13 21:05           ` Drew Adams
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR10MB5488A6CC22DD05739EF95A80F3CB9@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.