incorrect encoding in command mode

[SolitaryN]

Feature description

like in normal mode to type:
:!gcc % && a.out

Additional information

No response

[SolitaryN]

I can run it in nvim, but i can't get the right react and answer of the command

[CharlesChiuGit]

No idea what your desire result is. please be specific.

[ayamir]

Your command is incorrect. The correct way is !gcc % && ./a.out. BTW, I don't know this command whether works on windows.

[SolitaryN]

Oops, that's my fault, i didn't not realize that it is Windows. And the correct command in Windows is :!gcc % && .\a.exe

[CharlesChiuGit]

@SolitaryN so is the problem solved?

[SolitaryN]

But there are still some problem in the text format generated by the command in Windows. like below:

the command output format in nvim is not right.

[CharlesChiuGit]

can confirmed. it happens in other places too, for example, plugin installation failed, but i'm not sure how to fix it. it seems like an encoding issue.

[Jint-lzxy]

We need some additional information (fill in all queries that are in bold [i.e., replace <your-response> with your answer] and tick all applicable checkboxes):

Raw markdown (please copy this)

- **Your $TERM environment variable:** _\<your-response\>_
- **Your operating system & version:** _\<your-response\>_
- [ ] My `nvim` supports multibyte text processing (`:echo has("multi_byte")` returns 1).
- [ ] This issue **can** be reproduced using other terminal emulators.
- [ ] The following command works as expected in PowerShell _(i.e., pwsh renders those texts and icons correctly. When applicable, icons are very close to the crosses but there is no overlap)_:
```pwsh
Write-Host ("E492：不是编辑器的命令", "", "", "", "XXXXXXXXX") -Separator " || "
```
- [ ] The above command works as expected in `nvim` (command mode).
- **The output of the following command in PowerShell is:** _\<your-response\>_
```pwsh
Write-Host ($OutputEncoding, [System.Console]::InputEncoding, [System.Console]::OutputEncoding) -Separator " | "
```
- **The output of the above command in `nvim` command mode is:** _\<your-response\>_
- **The output of the following commands in neovim:**
  - `:set encoding?`:  _\<your-response\>_
  - `:language`: _\<your-response\>_
  - `:set fileencodings?`: _\<your-response\>_

---

Preview:

• Your $TERM environment variable: <your-response>
• Your operating system & version: <your-response>
• My nvim supports multibyte text processing (:echo has("multi_byte") returns 1).
• This issue can be reproduced using other terminal emulators.
• The following command works as expected in PowerShell (i.e., pwsh renders those texts and icons correctly. When applicable, icons are very close to the crosses but there is no overlap):

Write-Host ("E492：不是编辑器的命令", "", "", "", "XXXXXXXXX") -Separator " || "

• The above command works as expected in nvim (command mode).
• The output of the following command in PowerShell is: <your-response>

Write-Host ($OutputEncoding, [System.Console]::InputEncoding, [System.Console]::OutputEncoding) -Separator " | "

• The output of the above command in nvim command mode is: <your-response>
• The output of the following commands in neovim:
  • :set encoding?: <your-response>
  • :language: <your-response>
  • :set fileencodings?: <your-response>

cc @CharlesChiuGit @SolitaryN

[CharlesChiuGit]

• Your $TERM environment variable: xterm-256color compatible^{1 2}
• Your operating system & version: Win11 Pro. 22H2, 22621.1555
• My nvim supports multibyte text processing (:echo has("multi_byte") returns 1).
• This issue can be reproduced using other terminal emulators.

Half right, half wrong.

In wezterm on win11:

• The following command works as expected in PowerShell (i.e., pwsh renders those texts and icons correctly. When applicable, icons are very close to the crosses but there is no overlap):

Write-Host ("E492：不是编辑器的命令", "", "", "", "XXXXXXXXX") -Separator " || "

They overlap.

Result:

• The above command works as expected in nvim (command mode).

it doesn't.

Result:

• The output of the following command in PowerShell is:

Write-Host ($OutputEncoding, [System.Console]::InputEncoding, [System.Console]::OutputEncoding) -Separator " | "

Result: (same in wezterm's pwsh)

• The output of the above command in nvim command mode is:

Result: (same in wezterm's pwsh)

• The output of the following commands in neovim:
  • :set encoding?: utf-8
  • :language: LC_COLLATE=zh_TW;LC_CTYPE=zh_TW;LC_MONETARY=zh_TW;LC_NUMERIC=C;LC_TIME=zh_TW
  • :set fileencodings?: ucs-bom,utf-8,default,latin1

Footnotes

1. https://superuser.com/questions/1691010/term-value-for-windows-10-terminal ↩

2. https://github.com/microsoft/terminal/issues/6045 ↩

[CharlesChiuGit]

My screenshots with black background are in wezterm, and those with purple background are in windows terminal.

[CharlesChiuGit]

@SolitaryN can u try this draft? #659

I would like to know if this draft can get the same result on your machine as mine.

[SolitaryN]

• Your $TERM environment variable: nothing was printed(echo $TERM)

• Your operating system & version: Windows10 22H2 19045.2604

• [ x] My nvim supports multibyte text processing (:echo has("multi_byte") returns 1).

• [x ] This issue can be reproduced using other terminal emulators.

• The following command works as expected in PowerShell (i.e., pwsh renders those texts and icons correctly. When applicable, icons are very close to the crosses but there is no overlap):
  

• The above command works as expected in nvim (command mode).
  

• The output of the following command in PowerShell is: _
  
  _

Write-Host ($OutputEncoding, [System.Console]::InputEncoding, [System.Console]::OutputEncoding) -Separator " | "

• The output of the above command in nvim command mode is:
• The output of the following commands in neovim:
  • :set encoding?: encoding=utf-8
  • :language:
  • :set fileencodings?: fileencodings=ucs-bom, utf-8,default,latin1

[CharlesChiuGit]

• Your $TERM environment variable: nothing was printed(echo $TERM)

• Your operating system & version: Windows10 22H2 19045.2604

• [ x] My nvim supports multibyte text processing (:echo has("multi_byte") returns 1).

• [x ] This issue can be reproduced using other terminal emulators.

• The following command works as expected in PowerShell (i.e., pwsh renders those texts and icons correctly. When applicable, icons are very close to the crosses but there is no overlap):

• The above command works as expected in nvim (command mode).

• The output of the following command in PowerShell is: _

_

Write-Host ($OutputEncoding, [System.Console]::InputEncoding, [System.Console]::OutputEncoding) -Separator " | "

• The output of the above command in nvim command mode is:

• The output of the following commands in neovim:

  • :set encoding?: encoding=utf-8

  • :language:

  • :set fileencodings?: fileencodings=ucs-bom, utf-8,default,latin1

I think u didn't install any nerdfont?

[SolitaryN]

I installed cascadia-code, it is nerd-font right?

[CharlesChiuGit]

I installed cascadia-code, it is nerd-font right?

it seems like u install it via scoop? i found the scoop version somehow looks different then directly downloaded and install the font from the official repo. can u try reinstall the nerdfont with this manner?( i'm using jetbtainsmono, maybe u can try it, i'm not sure if this make any difference.

also, did u set the font in windows terminal's shell profile?

[SolitaryN]

yes, i installed it via scoop and I set the font in windows terminal profile.

[CharlesChiuGit]

could u try install jetbrainsmono from the official nerdfont repo? tks!

[SolitaryN]

there are still wrong format in nvim

[SolitaryN]

whether have you had this wrong in your nvim on Windows?

there are still wrong format in nvim

[CharlesChiuGit]

i think u use the wrong name, check "font settings" to get the correct name.

[CharlesChiuGit]

whether have you had this wrong in your nvim on Windows?

there are still wrong format in nvim

check my above comment

[CharlesChiuGit]

@SolitaryN can u try this draft? #659

I would like to know if this draft can get the same result on your machine as mine.

this one

[CharlesChiuGit]

@SolitaryN so does the draft work?

[SolitaryN]

Actually not, I mean maybe it's not suitable to use it in Windows, I will try it in WSL2.

[SolitaryN]

thanks for your help and お世話になってすみませんでした、ありがとう

[CharlesChiuGit]

@SolitaryN I think u will be interested in #659 (comment).