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@jurta.org>
Cc: 'Kelly Dean' <kellydeanch@yahoo.com>, 12988@debbugs.gnu.org
Subject: bug#12988: [PATCH] RE: bug#12988: isearch fails to persistently indicate case sensitivity
Date: Thu, 29 Nov 2012 17:18:24 -0800	[thread overview]
Message-ID: <94CE113EBBE742F68D103EE3FC4E6541@us.oracle.com> (raw)
In-Reply-To: <87ehjc3q1j.fsf@mail.jurta.org>

> >  Isearch    - case sensitive,   strict whitespace
> >  ISEARCH    - case insensitive, strict whitespace
> >  I search   - case sensitive,   lax    whitespace
> >  I SEARCH   - case insensitive, lax    whitespace
> 
> ISEARCH is too loud.  All-caps text usually indicates SHOUTING ;-)
> 
> What do you think about altering only the capital letter:
> `Isearch' vs `isearch'.

I disagree, but please do whatever you like.  I disagree because the change from
one to the other is MUCH clearer using uppercase: There is far more visual
difference between Isearch and ISEARCH than between Isearch and isearch.

I agree that ALL CAPS IN TEXT IS LIKE SHOUTING.  This is not a paragraph,
however, but a short symbol.  And here we actually WANT to draw attention to the
change/difference (IMHO).  I, at lest, *want* the change to be easily to notice.

[FWIW, all caps is also a programming idiom as the way case-insensitive testing
is typically done (convert everything to uppercase, then test).  (Could equally
be lowercase, I guess, but uppercase seems to be what is used.)  So at least
some (esp. old perhaps) programmers associate UPPERCASE with case-insensitivity
(and even with old, uppercase-only languages and keyboards).]

But I have no objection to all lowercase instead of all uppercase.  I have no
objection to anything else you might choose.

I have no objection to:

 isearch    - case-insensitive
 Isearch    - case-sensitive
 I search   -                and lax whitespace
 I*search   -                and regexp
 I* search  -                and lax ws and regexp
 ...

or whatever.






  reply	other threads:[~2012-11-30  1:18 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 [this message]
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
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

  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=94CE113EBBE742F68D103EE3FC4E6541@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=12988@debbugs.gnu.org \
    --cc=juri@jurta.org \
    --cc=kellydeanch@yahoo.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 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).