From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Leonard Lausen <leonard@lausen.nl>, 27505@debbugs.gnu.org
Subject: bug#27505: LC_CTYPE affects tutorial language
Date: Sun, 17 Apr 2022 21:44:51 +0200 [thread overview]
Message-ID: <87y2035wb0.fsf_-_@gnus.org> (raw)
In-Reply-To: <83zibeuxpw.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 05 Aug 2017 13:15:39 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> The default behavior is very unlikely to change, sorry. It took us
> many years to arrive at the current behavior, so changing that for a
> single use case, even if it's deemed important, makes little sense to
> me.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
Skimming this bug report, I think the conclusion was that we don't want
to change how these variables work in Emacs at this point, so I'm
therefore closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-17 19:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871soq7pyr.fsf@users.sourceforge.net>
2017-06-27 14:48 ` bug#27505: LC_CTYPE affects tutorial language Leonard Lausen
2017-06-27 15:05 ` Eli Zaretskii
2017-06-27 15:13 ` Andreas Schwab
[not found] ` <handler.27505.C.150189707129878.notifdonectrl.0@debbugs.gnu.org>
2017-08-05 1:54 ` bug#27505: acknowledged by developer (Re: bug#27505: LC_CTYPE affects tutorial language) Leonard Lausen
2017-08-05 2:06 ` npostavs
2017-08-05 5:59 ` Leonard Lausen
2017-08-05 7:10 ` Eli Zaretskii
2017-08-05 7:06 ` Eli Zaretskii
2017-08-05 8:17 ` Leonard Lausen
2017-08-05 9:17 ` Eli Zaretskii
2017-08-05 9:52 ` Leonard Lausen
2017-08-05 10:15 ` Eli Zaretskii
2017-08-05 10:50 ` Leonard Lausen
2017-08-05 11:09 ` Andreas Schwab
2017-08-05 11:20 ` Leonard Lausen
2017-08-05 11:22 ` Leonard Lausen
2022-04-17 19:44 ` Lars Ingebrigtsen [this message]
2017-08-05 8:18 ` Leonard Lausen
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=87y2035wb0.fsf_-_@gnus.org \
--to=larsi@gnus.org \
--cc=27505@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=leonard@lausen.nl \
/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).