From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: senkijun@gmail.com, ruijie@netyu.xyz, yantar92@posteo.net,
64652@debbugs.gnu.org
Subject: bug#64652: 28.2; Adding a property bug on Windows 11
Date: Sun, 16 Jul 2023 14:36:06 +0300 [thread overview]
Message-ID: <83y1jg84wp.fsf@gnu.org> (raw)
In-Reply-To: <13BD5663-B051-4FFC-BEE5-1768EABF8C0E@gmail.com> (message from Mattias Engdegård on Sun, 16 Jul 2023 13:07:01 +0200)
> From: Mattias Engdegård <mattias.engdegard@gmail.com>
> Date: Sun, 16 Jul 2023 13:07:01 +0200
> Cc: Eli Zaretskii <eliz@gnu.org>,
> senkijun@gmail.com,
> ruijie@netyu.xyz,
> 64652@debbugs.gnu.org
>
> In general we should make an effort to stop the user's locale leaking into elisp code logic. Ideally, case-folding should be property of a regexp or part of it, not controlled by a user-customisable global variable.
That would be equivalent of wrapping some/many of the regexp searches
with with-case-table. While I agree that it would be cleaner in the
code, the performance concerns Ihor expressed will still be there.
Btw, achieving what you want should be relatively easy: just make the
case-table the property of the regexp, and teach compile_pattern and
friends to look at that, in preference to the buffer's case-table,
when deciding which case-table to use.
> I'm just waiting for the horde of irate Turkish Pascal programmers to complain about broken font-lock.
That should have happened about 20 years ago.
next prev parent reply other threads:[~2023-07-16 11:36 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 13:27 bug#64652: 28.2; Adding a property bug on Windows 11 Senki Jun
2023-07-15 17:07 ` Ruijie Yu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-15 17:18 ` Ihor Radchenko
2023-07-15 18:53 ` Eli Zaretskii
2023-07-15 19:24 ` Senki Jun
2023-07-15 20:09 ` Senki Jun
2023-07-16 5:03 ` Eli Zaretskii
2023-07-16 5:59 ` Ihor Radchenko
2023-07-16 6:16 ` Senki Jun
2023-07-16 6:34 ` Ihor Radchenko
2023-07-16 6:40 ` Senki Jun
2023-07-16 6:44 ` Ihor Radchenko
2023-07-16 6:56 ` Senki Jun
2023-07-16 7:12 ` Senki Jun
2023-07-16 7:15 ` Ihor Radchenko
2023-07-16 7:20 ` Senki Jun
2023-07-16 7:29 ` Eli Zaretskii
2023-07-16 7:31 ` Senki Jun
2023-07-16 7:33 ` Senki Jun
2023-07-16 7:37 ` Ihor Radchenko
2023-07-16 7:52 ` Eli Zaretskii
2023-07-16 8:07 ` Ihor Radchenko
2023-07-16 8:16 ` Senki Jun
2023-07-16 8:40 ` Eli Zaretskii
2023-07-16 8:56 ` Senki Jun
2023-07-16 8:56 ` Ihor Radchenko
2023-07-16 9:03 ` Eli Zaretskii
2023-07-16 9:09 ` Eli Zaretskii
2023-07-16 9:20 ` Ihor Radchenko
2023-07-16 9:21 ` Ihor Radchenko
2023-07-16 10:21 ` Eli Zaretskii
2023-07-16 10:25 ` Ihor Radchenko
2023-07-16 11:07 ` Mattias Engdegård
2023-07-16 11:36 ` Eli Zaretskii [this message]
2023-07-16 12:11 ` Ihor Radchenko
2023-07-16 12:59 ` Eli Zaretskii
2023-07-16 13:06 ` Ihor Radchenko
2023-07-16 13:40 ` Eli Zaretskii
2023-07-16 17:16 ` Senki Jun
2023-07-16 9:04 ` Ihor Radchenko
2023-07-16 7:23 ` Eli Zaretskii
2023-07-16 7:26 ` Eli Zaretskii
2023-07-16 7:25 ` Eli Zaretskii
2023-07-16 4:47 ` Eli Zaretskii
[not found] ` <87wmz0mma4.fsf@localhost>
2023-07-16 7:24 ` Eli Zaretskii
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=83y1jg84wp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64652@debbugs.gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=ruijie@netyu.xyz \
--cc=senkijun@gmail.com \
--cc=yantar92@posteo.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).