From: Bastien <bastienguerry@googlemail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Improve the docstring of case-fold-search
Date: Tue, 28 Jul 2009 05:01:30 +0800 [thread overview]
Message-ID: <87tz0x925d.fsf@bzg.ath.cx> (raw)
In-Reply-To: <jwv63de2g2x.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Mon, 27 Jul 2009 13:27:48 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> The case-fold-search variable is pretty low-level and applies to
>>> functions like re-search-forward. Maybe it shouldn't be customizable to
>>> avoid such confusion.
>> As a first step toward this,
>
> I don't see why you'd need steps for this.
As I understand it, the goal is to turn case-fold-search into a
non-customizable variable. To me it makes only sense if the user
is still able to configure the way he wants the interactive search
to behave. Hence the "step" of finding the right way to turn
`isearch-case-fold-search' into an option.
>> the attached patch creates an option for
>> `isearch-case-fold-search'. The possible values for this option are:
>
>> t : isearch ignores case
>> nil : isearch does not ignore case
>> 'yes : isearch ignores mixed case
>> 'case-fold-search : isearch uses the local case-fold-search
>
>> Is it okay to apply this?
>
> I don't understand what use cases we're trying to address here.
The case where `case-fold-search' is not configurable anymore and the
user want to customize the default behavior of the interactive search.
Does that make more sense?
--
Bastien
prev parent reply other threads:[~2009-07-27 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 2:17 Improve the docstring of case-fold-search Bastien
2009-07-22 3:11 ` Eli Zaretskii
2009-07-22 3:38 ` Stefan Monnier
2009-07-22 8:11 ` Bastien
2009-07-27 2:42 ` Bastien
2009-07-27 17:27 ` Stefan Monnier
2009-07-27 21:01 ` Bastien [this message]
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=87tz0x925d.fsf@bzg.ath.cx \
--to=bastienguerry@googlemail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).