unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Bastos <dbastos@id.uff.br>
Cc: 58281@debbugs.gnu.org, dbastos@toledo.com
Subject: bug#58281: 27.1; windows mangles encoding on command line
Date: Wed, 12 Oct 2022 11:45:36 +0300	[thread overview]
Message-ID: <83k055ctvz.fsf@gnu.org> (raw)
In-Reply-To: <CAEQ-z=JHDFaj3S373bvAV+PK8WU8jayXZh51URODwGEr3eAo=A@mail.gmail.com> (message from Daniel Bastos on Thu, 6 Oct 2022 09:03:50 -0300)

> From: Daniel Bastos <dbastos@id.uff.br>
> Date: Thu, 6 Oct 2022 09:03:50 -0300
> Cc: Wayne Harris <dbastos@toledo.com>, 58281@debbugs.gnu.org
> 
> On Tue, Oct 4, 2022 at 7:02 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > > From: Wayne Harris <dbastos@toledo.com>
> > > Date: Mon, 03 Oct 2022 22:18:35 -0300
> > >
> > > I run emacs -Q.  I open eshell.  Then I try to use fossil (which is a
> > > version control system like git) and try to put accented letters on the
> > > commit message.  No choice of encoding seems to avoid the mangling.
> > >
> > > c:/my/path $ alias fs 'fossil $*'
> > > c:/my/path $ echo kkk >> encoding.txt
> > > c:/my/path $ fs changes
> > > EDITED     encoding.txt
> > >
> > > c:/my/path $ (print default-process-coding-system)
> > > (undecided-dos . undecided-unix)
> > >
> > > c:/my/path $ (or buffer-file-coding-system "it is nil")
> > > it is nil
> > >
> > > c:/my/path $ fs commit -m 'Naiveté'
> > > [...]
> > > Sync done, wire bytes sent: 3234  received: 309  ip: 5.161.138.46
> > >
> > > c:/my/path $ fs timeline -n 1
> > > === 2022-10-02 ===
> > > 13:11:20 [febbbf0441] *CURRENT* Naiveté (user: mer tags: trunk)
> > > --- entry limit (1) reached ---
> > > c:/my/path $
> >
> > Where did you download Fossil for MS-Windows?  Is it a native Windows
> > program, or a Cygwin program?  Is 'fs' a program (i.e. fs.exe) or some
> > kind of shell script, and if the latter, can you post the script?
> 
> I went to
> 
>   https://fossil-scm.org/home/uv/download.html
> 
> and chose the last one --- Windows64 ---, which is the ZIP at
> 
>   https://fossil-scm.org/home/uv/fossil-w64-2.19.zip
> 
> Inside this ZIP, there's a fossil.exe binary.  All evidence points to
> a native Windows program, not a Cygwin program.
> 
> %file c:/my/path/fossil.exe
> c:/my/path/fossil.exe: PE32+ executable (console) x86-64, for MS Windows
> %
> 
> There's no fs.exe and no script fs.  (Sorry about that.)  That's just
> my alias in ESHELL.  You can safely assume that /fs/ just means
> /fossil/.  (I shouldn't have used the alias in this bug report.
> Sorry.)
> 
> > Also, do you know whether Fossil expects the message text in some
> > particular encoding?
> 
> That I don't know.  I've looked into the documentation, but I did not
> find anything that looked relevant.  I did find old commit messages in
> the repository of fossil itself that little by little the developers
> have been adding UTF-8 support to it.  But I can't say it expects any
> particular encoding.

I think you said at some point that using non-ASCII commit log
messages from a shell outside of Emacs did succeed?  If so, can you
describe how you do that, i.e. which shell do you use and how you type
'Naiveté' from the shell?  Also, what does the command "chcp" report
in that shell, if you invoke it with no arguments?





  reply	other threads:[~2022-10-12  8:45 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-04  1:18 bug#58281: 27.1; windows mangles encoding on command line Wayne Harris
2022-10-04 10:02 ` Eli Zaretskii
2022-10-06 12:03   ` Daniel Bastos
2022-10-12  8:45     ` Eli Zaretskii [this message]
2022-10-12 11:49       ` Daniel Bastos
2022-10-12 16:35         ` Eli Zaretskii
2022-10-12 16:54         ` Eli Zaretskii
2022-10-15 11:02           ` Eli Zaretskii
2022-11-06  7:20             ` Eli Zaretskii
2022-11-07 19:40               ` Daniel Bastos
2022-11-07 20:10                 ` Eli Zaretskii
2022-11-07 22:38                   ` Daniel Bastos
2022-11-08 12:08                     ` Eli Zaretskii
2023-09-03  9:26                       ` Stefan Kangas
2022-11-07 20:23                 ` Eli Zaretskii
2022-11-07 22:42                   ` Daniel Bastos
2022-11-08 12:09                     ` 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=83k055ctvz.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58281@debbugs.gnu.org \
    --cc=dbastos@id.uff.br \
    --cc=dbastos@toledo.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).