[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#23075: 24.5; vc-git-command should use coding-system-for-read
From: |
Óscar Fuentes |
Subject: |
bug#23075: 24.5; vc-git-command should use coding-system-for-read |
Date: |
Mon, 21 Mar 2016 20:38:22 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.92 (gnu/linux) |
Eli Zaretskii <eliz@gnu.org> writes:
>> Does git always use that encoding? If not, on what it depends the
>> encoding used by git?
>
> It just spews the bytes, AFAIK. IOW, it's the encoding of the file
> whose log we are viewing.
I was expecting from HELLO to be utf-8, but you are right.
Please note that a diff may contain changes from multiple files,
including some that do not longer exists (or that exists with another
encoding). So we can't process a diff as a single unit, it must be
separated by file.
Solving this on a general way does not seem possible, but we can do our
best by using the file's current encoding, or simply guessing it. The
former can have serious performance implications.
- bug#23075: 24.5; vc-git-command should use coding-system-for-read, Nikolay Kudryavtsev, 2016/03/21
- bug#23075: 24.5; vc-git-command should use coding-system-for-read, Eli Zaretskii, 2016/03/21
- bug#23075: 24.5; vc-git-command should use coding-system-for-read, Eli Zaretskii, 2016/03/21
- bug#23075: 24.5; vc-git-command should use coding-system-for-read, Nikolay Kudryavtsev, 2016/03/21
- bug#23075: 24.5; vc-git-command should use coding-system-for-read, Eli Zaretskii, 2016/03/21
- bug#23075: 24.5; vc-git-command should use coding-system-for-read, Nikolay Kudryavtsev, 2016/03/21