From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Bastos <dbastos@id.uff.br>
Cc: 58281@debbugs.gnu.org
Subject: bug#58281: 27.1; windows mangles encoding on command line
Date: Mon, 07 Nov 2022 22:23:49 +0200 [thread overview]
Message-ID: <83v8nqy0mi.fsf@gnu.org> (raw)
In-Reply-To: <CAEQ-z=Kth8mwEuwLfA-NCGC0s6=wGBqra8Bcfha0EcG+N5Y6hQ@mail.gmail.com> (message from Daniel Bastos on Mon, 7 Nov 2022 16:40:04 -0300)
> From: Daniel Bastos <dbastos@id.uff.br>
> Date: Mon, 7 Nov 2022 16:40:04 -0300
> Cc: 58281@debbugs.gnu.org
>
> > > I've now installed a change for Emacs 29 that I think should fix your
> > > problems. So if you can try the current master branch of the Emacs
> > > Git repository, please do, and see if your problem with Fossil are
> > > solved there.
>
> I'm not sure which is "Emacs 29". I took the master branch
>
> https://git.savannah.gnu.org/cgit/emacs.git/
>
> right now --- November 7th, 15h EST --- and followed nt/INSTALL.W64 to
> compile it using MSYS32 in a MINGW64 shell. After building the
> runemacs.exe, I ran it with the option -Q and I see the version is
>
> GNU Emacs 29.0.50 (build 1, x86_64-w64-mingw32) of 2022-11-07
>
> I get the following behavior:
Btw, what is the value of locale-coding-system in this case for you in
Emacs 29?
next prev parent reply other threads:[~2022-11-07 20:23 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v8nqy0mi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58281@debbugs.gnu.org \
--cc=dbastos@id.uff.br \
/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.