From: Tino Calancha <tino.calancha@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ynyaaa@gmail.com, Tino Calancha <tino.calancha@gmail.com>,
schwab@linux-m68k.org, 26580@debbugs.gnu.org, juri@linkov.net
Subject: bug#26580: 25.1; inappropriate case folding while isearch-forward-regexp
Date: Fri, 21 Apr 2017 23:59:23 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1704212343140.15176@calancha-pc> (raw)
In-Reply-To: <83mvb9ao3t.fsf@gnu.org>
On Fri, 21 Apr 2017, Eli Zaretskii wrote:
>> From: Tino Calancha <tino.calancha@gmail.com>
>> Date: Fri, 21 Apr 2017 21:16:27 +0900 (JST)
>> Cc: ynyaaa@gmail.com, Tino Calancha <tino.calancha@gmail.com>,
>> 26580@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
>>
>> C-M-s \T ; matches lower and upper T
>> C-M-s T ; just matches upper T
>>
>> I don't see in the manual this effect on an escaped upper letter.
>
> (defcustom search-upper-case 'not-yanks
> "If non-nil, upper case chars disable case fold searching.
> That is, upper and lower case chars must match exactly.
> This applies no matter where the chars come from, but does not
> apply to chars in regexps that are prefixed with `\\'.
> If this value is `not-yanks', text yanked into the search string
> in Isearch mode is always downcased."
> :type '(choice (const :tag "off" nil)
> (const not-yanks)
> (other :tag "on" t)))
>
Great, thanks!
Now it's clear why \A matches both 'a' and 'A'.
next prev parent reply other threads:[~2017-04-21 14:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 17:55 bug#26580: 25.1; inappropriate case folding while isearch-forward-regexp ynyaaa
2017-04-21 3:40 ` Tino Calancha
2017-04-21 9:22 ` Andreas Schwab
2017-04-21 9:50 ` Tino Calancha
2017-04-21 12:04 ` Andreas Schwab
2017-04-21 12:16 ` Tino Calancha
2017-04-21 13:26 ` Eli Zaretskii
2017-04-21 14:59 ` Tino Calancha [this message]
2017-04-21 13:31 ` Andreas Schwab
2017-04-21 15:17 ` Tino Calancha
2017-04-21 17:42 ` Andreas Schwab
2017-04-25 20:57 ` Juri Linkov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1704212343140.15176@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=26580@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=schwab@linux-m68k.org \
--cc=ynyaaa@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.