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: Sun, 20 Nov 2016 17:32:07 -0500 [thread overview]
Message-ID: <CALO-gutinLO23U1Y=-JNR1M5V9uv=0C1NJGNpz+0GW7X84c2EA@mail.gmail.com> (raw)
In-Reply-To: <83bmxffaev.fsf@gnu.org>
On Wed, Nov 16, 2016 at 3:16 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>>
>> >> (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?
>
> Using setq-default.
Sorry for being thick, but which variable?
>> > 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?
>
> Languages that use utf-8 should already encode in utf-8 by default.
> Which ones don't?
I can't reproduce any such problems so perhaps whatever made me add it
is no longer a problem... However, since I removed the UTF-8 language
setting on Windows I had one case which wasn't working right: I ran some
`git show ...` to look at a past change in a (utf-8 encoded) source
file; I ran it with `shell-command` and the resulting text that popped
up had some junk next to some non-ascii characters. I'm pretty sure
that I didn't have such an issue with the setting on.
If this is not expected, I can try to get reproducible instructions.
--
((x=>x(x))(x=>x(x))) Eli Barzilay:
http://barzilay.org/ Maze is Life!
next prev parent reply other threads:[~2016-11-20 22:32 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
2016-11-16 20:16 ` Eli Zaretskii
2016-11-20 22:32 ` Eli Barzilay [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CALO-gutinLO23U1Y=-JNR1M5V9uv=0C1NJGNpz+0GW7X84c2EA@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.