[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: |
Wed, 27 Jul 2016 08:56:31 -0300 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.3 (windows-nt) |
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Daniel Bastos <dbastos@toledo.com>
>> Date: Tue, 26 Jul 2016 13:49:15 -0300
>>
>> > 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.
>
> How can it go "straight"?
I meant not being messed with. I don't know anything about MS-Windows.
In UNIX the creation of a new process by a shell is likely to call
execve, which won't touch the caller strings passed in through the
argv-argument.
- on eshell's encoding, Daniel Bastos, 2016/07/26
- Re: on eshell's encoding, Eli Zaretskii, 2016/07/26
- Message not available
- Message not available
- Re: on eshell's encoding,
Daniel Bastos <=
- 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