On Wed, 15 Jun 2022 10:04:07 +0900
Takashi Yano wrote:
> On Tue, 14 Jun 2022 21:56:39 +
> 5990 wrote:
> > I ran all commands on cmd from within Windows Terminal. Note that running
> > cmd.exe directly, and running cmd from the Windows Terminal is not the
> > same. cmd.exe does not support ANS
On Tue, 14 Jun 2022 21:56:39 +
5990 wrote:
> I ran all commands on cmd from within Windows Terminal. Note that running
> cmd.exe directly, and running cmd from the Windows Terminal is not the same.
> cmd.exe does not support ANSI codes.
My question was:
What shell (command user interface) di
Ignore my previous email; I forgot to enable plain text mode.
I ran all commands on cmd from within Windows Terminal. Note that running
cmd.exe directly, and running cmd from the Windows Terminal is not the same.
cmd.exe does not support ANSI codes.
Also, what do you mean you can't reproduce th
I ran all commands on cmd from within Windows Terminal. Note that running
cmd.exe directly, and running cmd from the Windows Terminal is not the same.
cmd.exe does not support ANSI codes.
Also, what do you mean you can't reproduce the issue? Was it because of
insufficient information, or becaus
On Tue, 14 Jun 2022 08:01:45 +
5990 via Cygwin wrote:
> ## Bug:
> Piping the standard output of cat into the standard input of golang or
> python, makes the Windows Terminal render ANSI codes as arrows.
>
> For example:
> `\033[36m` turns into `←[36m` (or in base64'd UNICODE: `4oaQWzM2bQ==`)
## Bug:
Piping the standard output of cat into the standard input of golang or python,
makes the Windows Terminal render ANSI codes as arrows.
For example:
`\033[36m` turns into `←[36m` (or in base64'd UNICODE: `4oaQWzM2bQ==`)
## Environment:
- cat v8.26
- Windows Terminal v1.12.10982.0
- golang
6 matches
Mail list logo
