[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: on eshell's encoding
From: |
Daniel Bastos |
Subject: |
Re: on eshell's encoding |
Date: |
Tue, 26 Jul 2016 13:49:15 -0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (windows-nt) |
Hi, Eli.
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Daniel Bastos <dbastos@toledo.com>
>> Date: Tue, 26 Jul 2016 11:25:55 -0300
>>
>> I'm running eshell. My current modeline is
>>
>> U\--- *eshell* [...]
>>
>> But after a git commit, I get garbage out from my utf-8 string given in
>> the command line. It must be git's fault. Do you confirm? (I don't
>> have the same problem if I input the string in a file.)
>>
>> %gc -a -m 'Função pra esvaziar a fila.'
>> [cooper 95bca82] Função pra esvaziar a fila.
>> 2 files changed, 5 insertions(+), 1 deletion(-)
>> %
>
> Is this on MS-Windows? If so, you cannot invoke programs from Emacs
> with command-line arguments encoded in anything but the system
> codepage. And UTF-8 cannot be a system codepage on Windows.
You're right. This is MS-Windows. But I thought MS-Windows would not
interfere here. Why does it interfere? I thought the messages would go
straight into git's ARGV. Does Windows read() and write() interpret the
bytes?
> I suggest to put the commit message in a file and use the -F switch to
> "git commit". Or use the built-in VC commands, they will do this
> automatically for you (if you have Emacs 25).
If I put the commit message in a file, even without using -F switch, it
works as expected.
(*) Version
GNU Emacs 24.3.1 (i386-mingw-nt6.2.9200) of 2013-03-17 on MARVIN
- on eshell's encoding, Daniel Bastos, 2016/07/26
- Re: on eshell's encoding, Eli Zaretskii, 2016/07/26
- Message not available
- Re: on eshell's encoding,
Daniel Bastos <=
- Message not available
- Re: on eshell's encoding, Daniel Bastos, 2016/07/27
- Re: on eshell's encoding, Yuri Khan, 2016/07/27
- Re: on eshell's encoding, Eli Zaretskii, 2016/07/27
- Re: on eshell's encoding, Yuri Khan, 2016/07/27
- Re: on eshell's encoding, Eli Zaretskii, 2016/07/27
- Re: on eshell's encoding, Eli Zaretskii, 2016/07/27