utf-8 is not working in terminal #14724

Closed
opened 2026-01-31 04:17:52 +00:00 by claunia · 5 comments
Owner

Originally created by @dongleiw on GitHub (Jul 29, 2021).

Windows Terminal version (or Windows build number)

1.10.1933.0

Other Software

tmux-1.8-4.el7.x86_64

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 9 2019 03:17:15)

Steps to reproduce

  1. create a file with content '# 哈哈'
  2. open it with vim out of tmux. displayed with '# �SH�SH'
  3. open it with vim in tmux. displayed with '# 哈哈'

Expected Behavior

open file a out of tmux . display with '# 哈哈'

Actual Behavior

open it with vim out of tmux. displayed with '# �SH�SH'

Originally created by @dongleiw on GitHub (Jul 29, 2021). ### Windows Terminal version (or Windows build number) 1.10.1933.0 ### Other Software tmux-1.8-4.el7.x86_64 VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 9 2019 03:17:15) ### Steps to reproduce 1. create a file with content '# 哈哈' 2. open it with vim out of tmux. displayed with '# �~S~H�~S~H' 3. open it with vim in tmux. displayed with '# 哈哈' ### Expected Behavior open file `a` out of tmux . display with '# 哈哈' ### Actual Behavior open it with vim out of tmux. displayed with '# �~S~H�~S~H'
Author
Owner

@zadjii-msft commented on GitHub (Aug 2, 2021):

Just to be sure, you're running vim in WSL, correct?

Can you do a hexdump on the file and share the output, so we can see what the raw bytes are?

@zadjii-msft commented on GitHub (Aug 2, 2021): Just to be sure, you're running `vim` in WSL, correct? Can you do a `hexdump` on the file and share the output, so we can see what the raw bytes are?
Author
Owner

@ghost commented on GitHub (Aug 6, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Aug 6, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Author
Owner

@dongleiw commented on GitHub (Aug 7, 2021):

Just to be sure, you're running vim in WSL, correct?

Can you do a hexdump on the file and share the output, so we can see what the raw bytes are?

Yes in WSL2. It shows correctly If I use virtrualbox instead
hexdump

0000000 2023 93e5 e588 8893 000a
0000009

Update steps to reproduce:

  1. login to WSL2
  2. ssh to another linux server
  3. create the file
  4. open it with vim out of tmux. displayed with '# �SH�SH'
  5. open it with vim in tmux. displayed with '# 哈哈'
@dongleiw commented on GitHub (Aug 7, 2021): > Just to be sure, you're running `vim` in WSL, correct? > > Can you do a `hexdump` on the file and share the output, so we can see what the raw bytes are? Yes in WSL2. It shows correctly If I use virtrualbox instead hexdump ``` 0000000 2023 93e5 e588 8893 000a 0000009 ``` Update steps to reproduce: 1. login to WSL2 2. ssh to another linux server 3. create the file 4. open it with vim out of tmux. displayed with '# �SH�SH' 5. open it with vim in tmux. displayed with '# 哈哈'
Author
Owner

@zadjii-msft commented on GitHub (Aug 10, 2021):

Thanks for that. Out of curiousity, what do you have LANG, LC_ALL set to? Does launching tmux with tmux -u (after closing all sessions) resolve the issue?

@zadjii-msft commented on GitHub (Aug 10, 2021): Thanks for that. Out of curiousity, what do you have `LANG`, `LC_ALL` set to? Does launching tmux with [`tmux -u`](https://askubuntu.com/questions/410048/utf-8-character-not-showing-properly-in-tmux) (after closing all sessions) resolve the issue?
Author
Owner

@ghost commented on GitHub (Aug 14, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Aug 14, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14724