From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: senkijun@gmail.com, ruijie@netyu.xyz,
mattias.engdegard@gmail.com, 64652@debbugs.gnu.org
Subject: bug#64652: 28.2; Adding a property bug on Windows 11
Date: Sun, 16 Jul 2023 13:06:48 +0000 [thread overview]
Message-ID: <87351o2efr.fsf@localhost> (raw)
In-Reply-To: <83ttu4811d.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> As we saw in this report, the default locale captured by Emacs from
>> Windows only changed in Windows 11.
>
> I'm talking about users of Emacs on Posix machines. I believe the
> Turkish locale existed on GNU/Linux for a long time.
Then, I am curious how Turkish locale did not cause a huge influx of bug
reports. Of course, this question is rather orthogonal to resolving this
bug report.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-07-16 13:06 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
2023-07-16 12:11 ` Ihor Radchenko
2023-07-16 12:59 ` Eli Zaretskii
2023-07-16 13:06 ` Ihor Radchenko [this message]
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=87351o2efr.fsf@localhost \
--to=yantar92@posteo.net \
--cc=64652@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=ruijie@netyu.xyz \
--cc=senkijun@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).