GNU bug report logs - #3616
23.0.94; vc-bzr coding system bug

Previous Next

Full log

Message #36 received at 3616-close <at> debbugs.gnu.org (full text, mbox):

From: Sean Whitton <spwhitton <at> spwhitton.name>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: duanpanda <at> gmail.com, 3616-close <at> debbugs.gnu.org
Subject: Re: bug#3616: Fwd: 3616 <at> debbugs.gnu.org
Date: Thu, 06 Mar 2025 09:07:04 +0800

Hello,

On Wed 05 Mar 2025 at 04:08pm +02, Eli Zaretskii wrote:

>> From: Sean Whitton <spwhitton <at> spwhitton.name>
>> Cc: Rui Duan <duanpanda <at> gmail.com>, 3616 <at> debbugs.gnu.org
>> Date: Wed, 05 Mar 2025 20:13:59 +0800
>>
>> Eli, this is a Windows thing, do you think there is something to
>> investigate and fix here, or perhaps this is already captured somewhere
>> else?
>
> I think the doc string of 'shell' already spells this out:
>
>   To specify a coding system for converting non-ASCII characters
>   in the input and output to the shell, use C-x RET c
>   before M-x shell.  You can also specify this with C-x RET p
>   in the shell buffer, after you start the shell.
>   The default comes from ‘process-coding-system-alist’ and
>   ‘default-process-coding-system’.
>
> Setting the correct encoding by default is a hard problem on Windows,
> since it is hard to know which process will want what encoding, and
> because UTF-8 cannot be easily used due to all kinds of subtle
> problems with how we launch subprocesses on Windows.  So I think users
> need either to set it manually or customize
> process-coding-system-alist for the programs they invoke frequently.

Thank you for confirming.

>> We should probably close this specific bug
>
> Yes.

Okay, doing so with this message.

-- 
Sean Whitton

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.