all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: on ESHELL, utf-8 and fossil command-line commit message
Date: Sat, 01 Oct 2022 22:18:22 +0300	[thread overview]
Message-ID: <83v8p39wu9.fsf@gnu.org> (raw)
In-Reply-To: <86wn9jbbt6.fsf@protonmail.com> (message from Wayne Harris via Users list for the GNU Emacs text editor on Sat, 01 Oct 2022 16:09:41 -0300)

> Date: Sat, 01 Oct 2022 16:09:41 -0300
> From:  Wayne Harris via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
> 
> > Maybe you have other customizations that cause this.  What does the
> > below say:
> >
> >   M-: default-process-coding-system RET
> 
> It says 
> 
> %(print default-process-coding-system)
> (utf-8-dos . utf-8-unix)
> %
> 
> I tried to change it to just cp1252.
> 
> --8<---------------cut here---------------start------------->8---
> %(setq default-process-coding-system (cons 'cp1252 'cp1252))

Too late, I think.

So I think the problem is that your customizations set up UTF-8
everywhere, and that causes the problems.  My suggestion is to start
from "emacs -Q", and if these commands work there, review your
customizations until you find those which get in the way.

If even "emacs -Q" doesn't work, I suggest to submit a bug report with
all the details.

In general, in core we don't pass arbitrary text via command-line
arguments on MS-Windows; instead, we write text to a temporary file
and ask the program to read text from there -- for this very reason.
Most VCS commands accept -f or -F switch telling them to read the log
message from a file; I suggest to use that instead of fighting the
UTF-8 uphill battle.

> %fs timeline -n 1
> === 2022-10-01 ===
> 19:04:34 [d992644b4b] *CURRENT* Naiveté. (user: mer tags: trunk)
> --- entry limit (1) reached ---

Could it be that 'fs' expects UTF-8?  Is that a native Windows port or
a Cygwin port?  The latter will probably expect UTF-8 on the command
line, and you cannot give it that.



  reply	other threads:[~2022-10-01 19:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01 14:19 on ESHELL, utf-8 and fossil command-line commit message Wayne Harris via Users list for the GNU Emacs text editor
2022-10-01 15:05 ` Eli Zaretskii
2022-10-01 18:29   ` Wayne Harris via Users list for the GNU Emacs text editor
2022-10-01 18:41     ` Eli Zaretskii
2022-10-01 19:09       ` Wayne Harris via Users list for the GNU Emacs text editor
2022-10-01 19:18         ` Eli Zaretskii [this message]
2022-10-02 13:35           ` Wayne Harris via Users list for the GNU Emacs text editor

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=83v8p39wu9.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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.