unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, Tino Calancha <tino.calancha@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: grep-command: Ignore case if case-fold-search is non-nil
Date: Sun, 18 Sep 2016 11:03:03 -0700	[thread overview]
Message-ID: <fcd88eef-d573-eae3-5d60-d0511ff5d738@cs.ucla.edu> (raw)
In-Reply-To: <83intti7wl.fsf@gnu.org>

Eli Zaretskii wrote:
> case-fold-search defaults to non-nil, so this would make "M-x grep"
> case-insensitive for many users.  I'm not sure they will like it.

Similarly for M-x grep-find and find's -i option, and for M-x vc-git-grep, and 
for M-x diff and diff's --ignore-case and --ignore-file-name-case options, and 
probably for other stuff.

It might be OK to add a new variable, which would have the effect of setting 
case-fold-search and all the other stuff, for users who want case-folding to be 
the default everywhere. But where would it stop? Would the new setting also have 
the effect of setting font-lock-keywords-case-fold-search, say?



  parent reply	other threads:[~2016-09-18 18:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-18  9:31 grep-command: Ignore case if case-fold-search is non-nil Tino Calancha
2016-09-18  9:57 ` Dmitry Gutov
2016-09-18 10:30   ` Tino Calancha
2016-09-18 10:52     ` Richard Copley
2016-09-18 11:09       ` Tino Calancha
2016-09-18 11:55         ` Dmitry Gutov
2016-09-18 14:45 ` Eli Zaretskii
2016-09-18 15:10   ` Tino Calancha
2016-09-18 16:52     ` Andreas Schwab
2016-09-18 18:03   ` Paul Eggert [this message]
2016-09-18 15:05 ` Drew Adams
2016-09-18 15:14   ` Tino Calancha
2016-09-18 15:39     ` Eli Zaretskii
2016-09-18 17:55     ` Drew Adams
2016-09-18 18:05       ` Tino Calancha
2016-09-18 18:16         ` Drew Adams

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=fcd88eef-d573-eae3-5d60-d0511ff5d738@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=tino.calancha@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 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).