Vim in Tmux shows extra space in the line marked with icon #8642

Closed
opened 2026-01-31 01:34:31 +00:00 by claunia · 5 comments
Owner

Originally created by @jingchangshi on GitHub (May 28, 2020).

Environment

Windows build number:

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19041.0 Microsoft Windows NT 10.0.19041.0

Windows Terminal version: 1.0.1401.0

OpenSSH version:

OpenSSH_for_Windows_8.1p1, LibreSSL 2.9.2

Vim version:

VIM - Vi IMproved 8.1 (2018 May 18, compiled Nov 14 2019 10:34:09)

Tmux version:

2.9

Steps to reproduce

  1. Open Windows Terminal
  2. ssh to a CentOS 7 server
  3. start tmux
  4. Inside tmux, start vim
  5. Use vim plugin vim-bookmark to mark a line. The marker is an Emoji. The Unicode of this Emoji is U+1F4CC.
  6. You can see strange rendering of this marked line.

Expected behavior

Use Vim to open a file without Tmux. Marking a line gives the expected behavior.

expected

Actual behavior

bug

Look at the line 801 and 834. The word do is changed to doo. The work vol_all is changed to vol_alll.

A similar issue was reported in #5947 . But without Tmux.

Originally created by @jingchangshi on GitHub (May 28, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment Windows build number: ``` Platform ServicePack Version VersionString -------- ----------- ------- ------------- Win32NT 10.0.19041.0 Microsoft Windows NT 10.0.19041.0 ``` Windows Terminal version: `1.0.1401.0` OpenSSH version: ``` OpenSSH_for_Windows_8.1p1, LibreSSL 2.9.2 ``` Vim version: ``` VIM - Vi IMproved 8.1 (2018 May 18, compiled Nov 14 2019 10:34:09) ``` Tmux version: ``` 2.9 ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> 1. Open Windows Terminal 2. ssh to a CentOS 7 server 3. start tmux 4. Inside tmux, start vim 5. Use vim plugin vim-bookmark to mark a line. The marker is an Emoji. The Unicode of this Emoji is U+1F4CC. 6. You can see strange rendering of this marked line. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> Use Vim to open a file without Tmux. Marking a line gives the expected behavior. ![expected](https://user-images.githubusercontent.com/9106886/83134412-e7e33100-a116-11ea-8e66-9dd47b025778.jpg) # Actual behavior <!-- What's actually happening? --> ![bug](https://user-images.githubusercontent.com/9106886/83134432-ef0a3f00-a116-11ea-9dac-2a1dca21e1bb.jpg) Look at the line 801 and 834. The word do is changed to doo. The work vol_all is changed to vol_alll. A similar issue was reported in #5947 . But without Tmux.
claunia added the Resolution-By-DesignNeeds-TriageNeeds-Tag-FixNeeds-Attention labels 2026-01-31 01:34:31 +00:00
Author
Owner

@jdebp commented on GitHub (May 28, 2020):

The default sign in the VIM bookmarks extension is U+2691, which clearly this is not. You will help the Microsoft people by telling them what character you have customized your bookmark sign to. This is not least so that they can determine who is disagreeing with whom about character widths.

@jdebp commented on GitHub (May 28, 2020): The [default sign in the VIM bookmarks extension](https://github.com/MattesGroeger/vim-bookmarks/blob/3adeae10639edcba29ea80dafa1c58cf545cb80e/plugin/bookmark.vim#L23) is U+2691, which clearly this is not. You will help the Microsoft people by telling them what character you have customized your bookmark sign to. This is not least so that they can determine who is disagreeing with whom about character widths.
Author
Owner

@DHowett commented on GitHub (May 28, 2020):

@jdebp thanks 😄

@DHowett commented on GitHub (May 28, 2020): @jdebp thanks :smile:
Author
Owner

@jingchangshi commented on GitHub (May 29, 2020):

The default sign in the VIM bookmarks extension is U+2691, which clearly this is not. You will help the Microsoft people by telling them what character you have customized your bookmark sign to. This is not least so that they can determine who is disagreeing with whom about character widths.

After changing to the default sign U+2691, it looks good. The sign U+1F4CC is the key.

@jingchangshi commented on GitHub (May 29, 2020): > The [default sign in the VIM bookmarks extension](https://github.com/MattesGroeger/vim-bookmarks/blob/3adeae10639edcba29ea80dafa1c58cf545cb80e/plugin/bookmark.vim#L23) is U+2691, which clearly this is not. You will help the Microsoft people by telling them what character you have customized your bookmark sign to. This is not least so that they can determine who is disagreeing with whom about character widths. After changing to the default sign U+2691, it looks good. The sign U+1F4CC is the key.
Author
Owner

@ankitbhatia commented on GitHub (May 29, 2020):

Here's another issue with neovim rendering of unicode characters

  • nvim --version: 0.4.3
  • vim -u DEFAULTS (version: ) behaves differently?
    no
  • Operating system/version: Windows 10/WSL2 -- Ubuntu 20.04
  • Terminal name/version:
  • $TERM: Microsoft Terminal Version: 1.0.1402.0

Steps to reproduce using nvim -u NORC

test.txt
load this file with nvim -u NORC test.txt in any wsl terminal on windows.

nvim -u NORC

Actual behaviour

When the cursor moves inside the parenthesis, the text shifts by one character.
image
image

Expected behaviour

Text should not shift by one character.

This is not a problem when running on an actual ubuntu distribution.

@ankitbhatia commented on GitHub (May 29, 2020): Here's another issue with neovim rendering of unicode characters - `nvim --version`: 0.4.3 - `vim -u DEFAULTS` (version: ) behaves differently? no - Operating system/version: Windows 10/WSL2 -- Ubuntu 20.04 - Terminal name/version: - `$TERM`: Microsoft Terminal Version: 1.0.1402.0 ### Steps to reproduce using `nvim -u NORC` [test.txt](https://github.com/neovim/neovim/files/4665273/test.txt) load this file with nvim -u NORC test.txt in any wsl terminal on windows. ``` nvim -u NORC ``` ### Actual behaviour When the cursor moves inside the parenthesis, the text shifts by one character. ![image](https://user-images.githubusercontent.com/3687273/82616099-47cb5c00-9b9a-11ea-9111-3b13da7e2159.png) ![image](https://user-images.githubusercontent.com/3687273/82616166-747f7380-9b9a-11ea-89db-385d5f172bd7.png) ### Expected behaviour Text should not shift by one character. This is not a problem when running on an actual ubuntu distribution.
Author
Owner

@DHowett commented on GitHub (Jun 2, 2020):

This is an unfortunate side effect of the application and the terminal disagreeing on how wide a character should be. Our character widths are reasonably up-to-date as of Unicode 13.0, so I'm just going to have to close this one by design with a hat tip to the terminal working group discussion about character widths[1] 😄

[1] https://gitlab.freedesktop.org/terminal-wg/specifications/-/issues/9

@DHowett commented on GitHub (Jun 2, 2020): This is an unfortunate side effect of the application and the terminal disagreeing on how wide a character should be. Our character widths are reasonably up-to-date as of Unicode 13.0, so I'm just going to have to close this one by design with a hat tip to the terminal working group discussion about character widths[1] :smile: [1] https://gitlab.freedesktop.org/terminal-wg/specifications/-/issues/9
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#8642