From: Michael Heerdegen <michael_heerdegen@web.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: 18018@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#18018: 24.4.50; (emacs) `Special Isearch'
Date: Sun, 01 May 2016 01:12:17 +0200 [thread overview]
Message-ID: <87eg9madym.fsf@web.de> (raw)
In-Reply-To: <685fb08c-2932-427f-abdb-e451213e9948@default> (Drew Adams's message of "Fri, 29 Apr 2016 15:41:59 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> Really? I don't have a build more recent than 2015-12-10, but in that
> build, at least, the identical text is still there, and I see nothing
> added about this being only the default behavior or about
> `case-fold-search'.
>
> But if this was really fixed, great.
Seems this has been fixed when the new char folding stuff has been
integrated. Now the relevant text is in (info "(emacs) Lax Search") and
reads like:
Searches in Emacs by default ignore the case of the text they are
searching through, if you specify the search string in lower case.
Thus, if you specify searching for ‘foo’, then ‘Foo’ and ‘foo’ also
match. Regexps, and in particular character sets, behave likewise:
‘[ab]’ matches ‘a’ or ‘A’ or ‘b’ or ‘B’. This feature is known as “case
folding”, and it is supported in both incremental and non-incremental
search modes.
An upper-case letter anywhere in the search string makes the search
case-sensitive. Thus, searching for ‘Foo’ does not find ‘foo’ or ‘FOO’.
This applies to regular expression search as well as to literal string
search. The effect ceases if you delete the upper-case letter from the
search string. The variable ‘search-upper-case’ controls this: if it is
non-‘nil’ (the default), an upper-case character in the search string
make the search case-sensitive; setting it to ‘nil’ disables this effect
of upper-case characters.
If you set the variable ‘case-fold-search’ to ‘nil’, then all letters
must match exactly, including case. This is a per-buffer variable;
altering the variable normally affects only the current buffer, unless
you change its default value. *Note Locals::. This variable applies to
nonincremental searches also, including those performed by the replace
commands (*note Replace::) and the minibuffer history matching commands
(*note Minibuffer History::).
Typing ‘M-c’ or ‘M-s c’ (‘isearch-toggle-case-fold’) within an
incremental search toggles the case sensitivity of that search. The
effect does not extend beyond the current incremental search, but it
does override the effect of adding or removing an upper-case letter in
the current search.
[...]
Michael.
prev parent reply other threads:[~2016-04-30 23:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 16:06 bug#18018: 24.4.50; (emacs) `Special Isearch' Drew Adams
2016-04-29 21:56 ` Lars Ingebrigtsen
2016-04-29 22:41 ` Drew Adams
2016-04-30 23:12 ` Michael Heerdegen [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=87eg9madym.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=18018@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
/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).