Unwanted characters printed when scrolling over non-alphanumeric characters when using tmux and emacs #3458

Closed
opened 2026-01-30 23:21:47 +00:00 by claunia · 2 comments
Owner

Originally created by @mbelmadani on GitHub (Aug 17, 2019).

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.295]
Windows Terminal version (if applicable): Version: 0.3.2171.0

Any other software?
GNU Emacs 24.3.1
tmux1.8
CentOS 7.0

Steps to reproduce

When I ssh to my CentOS 7.0 server and start a new tmux session (tmux new-session -s someSession), and open a new or existing file in emacs, every time I move my cursor on a white space or special character, I get a unwanted square character printed on the screen. Some characters are already there (e.g. on empty lines) when I first open the file. The changes are only visual and don't modify the actual text file (i.e. saving and re-opening the file clears the new characters) but those that are there when the file opens appear consistently, generally in empty lines.

If I try with emacs outside of tmux it works fine, so it seems to be specific to tmux or one of its setting.

I did try to set my $TERM to xterm-256color, rxvt, etc. in the tmux configs but it didn't seem to change anything.

Expected behavior

The text file should display as is without any additional characters, e.g.

image

Actual behavior

See screen shot and additional square characters:
image

Originally created by @mbelmadani on GitHub (Aug 17, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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 ```none Windows build number: Microsoft Windows [Version 10.0.18362.295] Windows Terminal version (if applicable): Version: 0.3.2171.0 Any other software? GNU Emacs 24.3.1 tmux1.8 CentOS 7.0 ``` # Steps to reproduce When I ssh to my CentOS 7.0 server and start a new tmux session (`tmux new-session -s someSession`), and open a new or existing file in emacs, every time I move my cursor on a white space or special character, I get a unwanted square character printed on the screen. Some characters are already there (e.g. on empty lines) when I first open the file. The changes are only visual and don't modify the actual text file (i.e. saving and re-opening the file clears the new characters) but those that are there when the file opens appear consistently, generally in empty lines. If I try with emacs outside of tmux it works fine, so it seems to be specific to tmux or one of its setting. I did try to set my `$TERM` to xterm-256color, rxvt, etc. in the tmux configs but it didn't seem to change anything. # Expected behavior The text file should display as is without any additional characters, e.g. ![image](https://user-images.githubusercontent.com/14117454/63214587-01a71080-c0cf-11e9-9ef6-618b3add0e62.png) # Actual behavior See screen shot and additional square characters: ![image](https://user-images.githubusercontent.com/14117454/63214584-ec31e680-c0ce-11e9-809f-a021e9b1aa38.png)
Author
Owner

@zadjii-msft commented on GitHub (Aug 19, 2019):

Can you try reproing this with the console (conhost.exe) instead of the Windows Terminal? You can get a conhost window by just opening wsl.exe directly.

This seems extra suspicious that it doesn't repro w/out tmux, but it'll certainly help narrow down our investigation if it's Windows Terminal specific o if this repros in conhost too.

@zadjii-msft commented on GitHub (Aug 19, 2019): Can you try reproing this with the console (conhost.exe) instead of the Windows Terminal? You can get a conhost window by just opening wsl.exe directly. This seems extra suspicious that it doesn't repro w/out tmux, but it'll certainly help narrow down our investigation if it's Windows Terminal specific o if this repros in conhost too.
Author
Owner

@ghost commented on GitHub (Aug 23, 2019):

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 23, 2019): 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#3458