From: "Drew Adams" <drew.adams@oracle.com>
To: "'Jambunathan K'" <kjambunathan@gmail.com>
Cc: 'Chong Yidong' <cyd@gnu.org>,
kellydeanch@yahoo.com, 12988@debbugs.gnu.org
Subject: bug#12988: [PATCH] RE: bug#12988: isearch fails to persistentlyindicate case sensitivity
Date: Sat, 1 Dec 2012 08:38:20 -0800 [thread overview]
Message-ID: <5DF7CF06569E4F599AF23E59A9AFF871@us.oracle.com> (raw)
In-Reply-To: <87pq2unqmt.fsf@gmail.com>
> It can go wherever.
>
> But key thing is there is this switchboard with a bunch of
> switches one for kitchen, one for hall etc. Then you walk
> to each of them and toggle them.
>
> So there are basically two commands - one to walk to next
> switch and one to toggle it. Switch themselves report whether
> they are ON/OFF and IN-FOCUS/OUT-OF-FOCUS. Choice of switches
> themselves become immaterial.
>
> If one wants a new control then all one has to think about is what
> character or glyph it will take and add it to the switchboard.
Yes, I understood that. I think it's a very good idea.
I also think the prompt is the best place for it.
Highlighting the current switches in some way is important to the usability of
it, I think.
It's perhaps worth pointing out that this can also obviate the use of the prompt
prefix "Regexp". And if we included other state indicators, such as
wrap/overwrap, it would obviate using their more verbose prompt indicators as
well.
That does not mean that we should remove the more verbose prompt hints - only
that we could. Best would be to let users optionally remove/add the redundant
more-verbose indicators (and optionally remove/add the new feature).
FWIW, in Isearch+ I highlight the prompt hints "Regexp", "Wrapped", and
"overwrapped", and I highlight the `Isearch' mode-line lighter using the same
face as each of those prompt qualifiers.
I mention that only to say that I think such a cue helps a user recognize the
state change - in particular wrt wrapping. (Have you ever continued searching a
few times after overwrapping without meaning to, because you did not immediately
notice the "overwrapped" hint?)
With such state indicators abbreviated a la your suggestion, highlighting the
appropriate state chars would be quite helpful, IMO.
Such a highlight lets a user notice the state change without requiring that s?he
actually look at the state indicator. IOW, it's an easy-to-perceive cue.
But such highlighting too should be customizable by users, of course. At least
by customizing their faces (including to `default', to selectively turn it off).
next prev parent reply other threads:[~2012-12-01 16:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 2:05 bug#12988: isearch fails to persistently indicate case sensitivity Kelly Dean
2012-11-25 9:54 ` Juri Linkov
2012-11-25 17:55 ` bug#12988: [PATCH] " Drew Adams
2012-11-25 18:02 ` bug#12988: [PATCH] RE: bug#12988: isearch fails to persistentlyindicate " Drew Adams
2012-11-28 23:19 ` bug#12988: [PATCH] RE: bug#12988: isearch fails to persistently indicate " Juri Linkov
2012-11-29 0:06 ` Drew Adams
2012-11-30 0:28 ` Juri Linkov
2012-11-30 1:18 ` Drew Adams
2012-11-30 1:34 ` Juri Linkov
2012-11-30 3:50 ` Drew Adams
2012-11-30 8:23 ` Eli Zaretskii
2012-11-30 8:35 ` Chong Yidong
2012-11-30 14:19 ` Stefan Monnier
2012-11-30 15:46 ` Dani Moncayo
2012-11-30 15:59 ` Dani Moncayo
2012-11-30 16:55 ` Stefan Monnier
2012-11-30 18:30 ` Juri Linkov
2012-11-30 19:26 ` Stefan Monnier
2012-11-30 19:44 ` Juri Linkov
2012-11-30 20:10 ` Stefan Monnier
2012-11-30 21:35 ` bug#12988: [PATCH] RE: bug#12988: isearch fails to persistentlyindicate " Drew Adams
2012-12-01 6:03 ` Chong Yidong
2012-12-01 6:41 ` Jambunathan K
2012-12-01 7:01 ` Drew Adams
2012-12-01 8:06 ` Jambunathan K
2012-12-01 16:38 ` Drew Adams [this message]
2012-11-30 8:36 ` bug#12988: [PATCH] RE: bug#12988: isearch fails to persistently indicate " Dani Moncayo
2012-11-30 9:56 ` Eli Zaretskii
2012-11-30 10:09 ` Dani Moncayo
2012-11-30 13:35 ` Andreas Schwab
2012-11-30 15:37 ` Dani Moncayo
2022-04-27 18: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=5DF7CF06569E4F599AF23E59A9AFF871@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=12988@debbugs.gnu.org \
--cc=cyd@gnu.org \
--cc=kellydeanch@yahoo.com \
--cc=kjambunathan@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 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.