GNU bug report logs - #12988
isearch fails to persistently indicate case sensitivity

Previous Next

Full log

Message #80 received at 12988 <at> debbugs.gnu.org (full text, mbox):

From: "Drew Adams" <drew.adams <at> oracle.com>
To: "'Stefan Monnier'" <monnier <at> iro.umontreal.ca>,
	"'Juri Linkov'" <juri <at> jurta.org>
Cc: 'Chong Yidong' <cyd <at> gnu.org>, kellydeanch <at> yahoo.com, 12988 <at> debbugs.gnu.org
Subject: RE: bug#12988: [PATCH] RE: bug#12988: isearch fails to
	persistentlyindicate case sensitivity
Date: Fri, 30 Nov 2012 13:35:53 -0800

> "Isearch/_" doesn't sound too bad, but indeed "Isearch/ " wouldn't
> work well.

The slash is useless anyway.  Why not consider the proposals discussed earlier
in the thread (repeated below)?  "I search" works fine, especially if the " " is
highlighted (the complete lighter also has a mouseover highlight).

 ISEARCH    - case-insensitive
 Isearch    - case-sensitive

Case-sensitive examples:

 I search   - lax whitespace
 I*search   - regexp
 I* search  - lax ws & regexp
 Isearchw   - word
 Isearch_   - symbol
 I searchw  - word & lax ws
 I search_  - symbol & lax ws

Case-insensitive is similar, with SEARCH instead of search.  E.g.,

 I* SEARCH  - lax ws & regexp

And each of the chars SPC _ w * could be highlighted, for increased clarity.

This convention uses a maximum of 2 more characters than what we use now, and it
covers everything discussed so far.

The notation used should be short.  It should be noticeable and recognizable for
someone who is familiar with the notation.

Less important is to have something that also suggests its meaning.  Why is that
less important?  Because once you learn the meaning, the suggestion is not
needed anymore, except as a reminder.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.