From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40216@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#40216: 28.0.50; Misinformation in isearch char-fold
Date: Fri, 27 Mar 2020 09:30:24 +0100 [thread overview]
Message-ID: <m2k1366vz3.fsf@gmail.com> (raw)
In-Reply-To: <83pncy8dlg.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 27 Mar 2020 10:24:27 +0300")
>>>>> On Fri, 27 Mar 2020 10:24:27 +0300, Eli Zaretskii <eliz@gnu.org> said:
>> From: Juri Linkov <juri@linkov.net>
>> Cc: Eli Zaretskii <eliz@gnu.org>, 40216@debbugs.gnu.org
>> Date: Fri, 27 Mar 2020 01:04:12 +0200
>>
>> I tried to find Røbert by typing Robert, but char-fold fails to find it.
>> A bug in char-fold?
Eli> I don't think it's a bug, because ø doesn't have a decomposition in
Eli> the Unicode character database:
Eli> (get-char-code-property ?ø 'decomposition) => (248)
Eli> (i.e. the character "decomposes" into itself). By contrast:
Eli> (get-char-code-property ?á 'decomposition) => (97 769)
Eli> (i.e. á decomposes into a followed by U+0301 COMBINING ACUTE ACCENT).
Eli> So if one wants to support the kind of folding you expected, one would
Eli> have to customize char-fold-include to add those additional rules.
Yes, wrong example. I guess this wouldnʼt be useful after all (and I
see nothing wrong with Juri's proposed fix to the actual issue).
Robert
next prev parent reply other threads:[~2020-03-27 8:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-24 23:00 bug#40216: 28.0.50; Misinformation in isearch char-fold Juri Linkov
2020-03-25 9:22 ` Robert Pluim
2020-03-25 20:29 ` Juri Linkov
2020-03-26 9:28 ` Robert Pluim
2020-03-26 14:25 ` Eli Zaretskii
2020-03-26 15:43 ` Robert Pluim
2020-03-26 23:04 ` Juri Linkov
2020-03-27 7:24 ` Eli Zaretskii
2020-03-27 8:30 ` Robert Pluim [this message]
2020-03-28 23:42 ` Juri Linkov
2020-03-26 23:00 ` 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
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=m2k1366vz3.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=40216@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
/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).