From: Eli Barzilay <eli@barzilay.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24953@debbugs.gnu.org
Subject: bug#24953: 25.1; Possible inefficiency in UTF-8
Date: Wed, 16 Nov 2016 14:59:58 -0500 [thread overview]
Message-ID: <CALO-guuP2sg-_Aq9oB=EguY+jUKgbsvSGGj_9rX_+racGXNrXw@mail.gmail.com> (raw)
In-Reply-To: <83eg2bfc51.fsf@gnu.org>
On Wed, Nov 16, 2016 at 2:38 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Eli Barzilay <eli@barzilay.org>
>> Date: Wed, 16 Nov 2016 14:11:57 -0500
>> Cc: 24953-done@debbugs.gnu.org
>>
>> > Regardless of the issue reported here, I would advise against setting
>> > the UTF-8 language environment on MS-Windows. [...]
>> > You shouldn't need to do this, not in Emacs 25 anyway.
>>
>> Is it a good idea to use it on linux?
>
> Yes. (And it should be the default on GNU/Linux, at least on most of
> its flavors.)
I built and installed 25.1, and it looks like the default is also
English. (At least according to `current-language-environment'.) Is
that a bug then?
>> (I originally thought that all it gets me is a default encoding for
>> non-ascii files...)
>
> You could customize just that, then.
Using `prefer-coding-system'? Or something else?
> And I don't really understand why that is needed, either, unless you
> want the files you create to be automatically in UTF-8.
Doesn't that make sense if I almost always edit source code for
languages that use utf-8 to read sources?
--
((x=>x(x))(x=>x(x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
next prev parent reply other threads:[~2016-11-16 19:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 4:25 bug#24953: 25.1; Possible inefficiency in UTF-8 Eli Barzilay
2016-11-16 16:17 ` Eli Zaretskii
2016-11-16 19:11 ` Eli Barzilay
2016-11-16 19:38 ` Eli Zaretskii
2016-11-16 19:59 ` Eli Barzilay [this message]
2016-11-16 20:16 ` Eli Zaretskii
2016-11-20 22:32 ` Eli Barzilay
2016-11-21 3:32 ` Eli Zaretskii
2016-11-21 21:38 ` Eli Barzilay
2016-11-22 3:33 ` Eli Zaretskii
2016-12-11 10:53 ` Eli Barzilay
2016-12-11 15:37 ` 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='CALO-guuP2sg-_Aq9oB=EguY+jUKgbsvSGGj_9rX_+racGXNrXw@mail.gmail.com' \
--to=eli@barzilay.org \
--cc=24953@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).