From: Juri Linkov <juri@linkov.net>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 22541@debbugs.gnu.org, Dima Kogan <dima@secretsauce.net>
Subject: bug#22541: 25.0.50; highlight-regexp from isearch has is case-sensitive even if case-fold is active
Date: Wed, 10 May 2017 01:10:03 +0300 [thread overview]
Message-ID: <87fugdfzoq.fsf@localhost> (raw)
In-Reply-To: <87bmrilylu.fsf@calancha-pc> (Tino Calancha's message of "Thu, 27 Apr 2017 23:22:05 +0900")
>>> @@ -1950,7 +1950,12 @@ isearch-highlight-regexp
>>> (regexp-quote s))))
>>> isearch-string ""))
>>> (t (regexp-quote isearch-string)))))
>>> - (hi-lock-face-buffer regexp (hi-lock-read-face-name)))
>>> + (hi-lock-face-buffer regexp (hi-lock-read-face-name)
>>> + (if (and (eq isearch-case-fold-search t)
>>> + search-upper-case)
>>> + (isearch-no-upper-case-p
>>> + isearch-string isearch-regexp)
>>> + isearch-case-fold-search)))
>>> (and isearch-recursive-edit (exit-recursive-edit)))
>>
>> If this works reliably, then we could remove that ugly hack
>> from ‘isearch-highlight-regexp’, I mean the one with the comment
>> “Turn isearch-string into a case-insensitive regexp”.
> That's right. We don't need such trick here anymore. But this hack
> turned ut to be useful in hi-lock.el.
>
> The new patch, in addition to fix this bug report, it also
> helps with the 5. in bug#22520, that is:
> emacs -Q
> M-s hr t RET RET ; Highlight with regexp "[Tt]"
> M-s hu t RET ; Unhighlight the buffer.
Thanks, could you find more test cases that still don't work?
next prev parent reply other threads:[~2017-05-09 22:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 6:29 bug#22541: 25.0.50; highlight-regexp from isearch has is case-sensitive even if case-fold is active Dima Kogan
2016-03-01 0:14 ` Juri Linkov
2016-04-27 5:02 ` Dima Kogan
2016-04-30 20:07 ` Juri Linkov
2020-05-21 23:23 ` Juri Linkov
2017-04-22 12:31 ` Tino Calancha
2017-04-23 23:18 ` Juri Linkov
2017-04-25 5:22 ` Tino Calancha
2017-04-25 20:52 ` Juri Linkov
2017-04-27 14:22 ` Tino Calancha
2017-05-09 22:10 ` Juri Linkov [this message]
2017-05-24 13:35 ` Tino Calancha
2017-05-25 12:11 ` Tino Calancha
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=87fugdfzoq.fsf@localhost \
--to=juri@linkov.net \
--cc=22541@debbugs.gnu.org \
--cc=dima@secretsauce.net \
--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).