all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daniel Bastos <dbastos@toledo.com>
To: help-gnu-emacs@gnu.org
Subject: Re: on eshell's encoding
Date: Wed, 27 Jul 2016 08:56:31 -0300	[thread overview]
Message-ID: <86zip3uweo.fsf@toledo.com> (raw)
In-Reply-To: mailman.2074.1469553449.26859.help-gnu-emacs@gnu.org

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.


  parent reply	other threads:[~2016-07-27 11:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-26 14:25 on eshell's encoding Daniel Bastos
2016-07-26 15:05 ` Eli Zaretskii
     [not found] ` <mailman.2058.1469545530.26859.help-gnu-emacs@gnu.org>
2016-07-26 16:49   ` Daniel Bastos
2016-07-26 17:17     ` Eli Zaretskii
2016-07-26 18:26       ` Yuri Khan
2016-07-26 18:35         ` Eli Zaretskii
     [not found]     ` <mailman.2074.1469553449.26859.help-gnu-emacs@gnu.org>
2016-07-27 11:56       ` Daniel Bastos [this message]
2016-07-27 13:15         ` Yuri Khan
2016-07-27 16:22           ` Eli Zaretskii
2016-07-27 16:47             ` Yuri Khan
2016-07-27 17:12               ` Eli Zaretskii
2016-07-27 16:14         ` Eli Zaretskii
     [not found]         ` <mailman.2119.1469636078.26859.help-gnu-emacs@gnu.org>
2016-08-02 13:24           ` Daniel Bastos
2016-08-02 15:12             ` 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=86zip3uweo.fsf@toledo.com \
    --to=dbastos@toledo.com \
    --cc=help-gnu-emacs@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.