unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Daniel Bastos <dbastos@toledo.com>
To: help-gnu-emacs@gnu.org
Subject: Re: on eshell's encoding
Date: Tue, 26 Jul 2016 13:49:15 -0300	[thread overview]
Message-ID: <864m7c5oqc.fsf@toledo.com> (raw)
In-Reply-To: mailman.2058.1469545530.26859.help-gnu-emacs@gnu.org

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



  parent reply	other threads:[~2016-07-26 16:49 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 [this message]
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
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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864m7c5oqc.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).