starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

SSH & emacs cause phantom characters when trying to scroll down #251

New Issue
Closed
opened 2026-01-30 21:46:52 +00:00 by claunia · 7 comments
claunia commented 2026-01-30 21:46:52 +00:00
Owner
Copy Link

Originally created by @Hyper200 on GitHub (May 10, 2018).

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    Version 10.0.16299.309

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)
    Using ssh, connect to a system and open a file using emacs, as you open the file press the down key to scroll.

capture

  • What's wrong / what should be happening instead:
    The file should open a scroll down, instead it adds a B to the top of the text file while it loads.

No entriley sure this is a console issue but the same issue dose not apply when using wsltty. Only seems to be an issue with emacs, I guess VI isn't in insert mode by default therefore it might not affect it.

Originally created by @Hyper200 on GitHub (May 10, 2018). * Your Windows build number: (Type ver at a Windows Command Prompt) Version 10.0.16299.309 * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) Using ssh, connect to a system and open a file using emacs, as you open the file press the down key to scroll. ![capture](https://user-images.githubusercontent.com/37409036/39864368-43491584-5441-11e8-8b3a-440242acd79b.PNG) * What's wrong / what should be happening instead: The file should open a scroll down, instead it adds a B to the top of the text file while it loads. No entriley sure this is a console issue but the same issue dose not apply when using wsltty. Only seems to be an issue with emacs, I guess VI isn't in insert mode by default therefore it might not affect it.
claunia commented 2026-01-30 21:46:54 +00:00
Author
Owner
Copy Link

@zadjii commented on GitHub (May 10, 2018):

What's TERM set to on the remote machine? A lot of issues like these are because the remote machine is set to something other than xterm-256color

@zadjii commented on GitHub (May 10, 2018): What's `TERM` set to on the remote machine? A lot of issues like these are because the remote machine is set to something other than `xterm-256color`
claunia commented 2026-01-30 21:46:54 +00:00
Author
Owner
Copy Link

@Hyper200 commented on GitHub (May 10, 2018):

Spot on

echo $TERM
xterm-256color

I guess the terminal has a general bug with xterm-256color? Or is there an altertive we should be setting.

xterm-256color must be the default for RHEL, CentOS etc.

@Hyper200 commented on GitHub (May 10, 2018): Spot on echo $TERM xterm-256color I guess the terminal has a general bug with xterm-256color? Or is there an altertive we should be setting. xterm-256color must be the default for RHEL, CentOS etc.
claunia commented 2026-01-30 21:46:54 +00:00
Author
Owner
Copy Link

@florian1984 commented on GitHub (Jul 10, 2018):

Im using vi with RHEL/SLES/Ubuntu, and got same problem (https://github.com/Microsoft/console/issues/188#issuecomment-391362285).

When I set => TERM="" => cursor key works, but page up/down not.
With TERM=xterm-color => page up/down works, cursor keys not

I could remap it in vimrc, but Im too lazy :-). With these bugs this m$ console is useless for me. Use now kitty (putty) again :-) ....

@florian1984 commented on GitHub (Jul 10, 2018): Im using vi with RHEL/SLES/Ubuntu, and got same problem (https://github.com/Microsoft/console/issues/188#issuecomment-391362285). When I set => TERM="" => cursor key works, but page up/down not. With TERM=xterm-color => page up/down works, cursor keys not I could remap it in vimrc, but Im too lazy :-). With these bugs this m$ console is useless for me. Use now kitty (putty) again :-) ....
claunia commented 2026-01-30 21:46:55 +00:00
Author
Owner
Copy Link

@Mythrix commented on GitHub (Jul 14, 2020):

Hmm I see that this issue is a year old, but I still have the same issue with emacs in CentOS 7.8 ssh'ed in from Windows Terminal.

When googling I found a thread for another console/terminal program ConEmu which had a similar issue with emacs: https://github.com/Maximus5/ConEmu/issues/1691

The top comment there seems to have some more detailed information about what the reason could be. Does that help in getting the issue fixed for Windows Terminal?

@Mythrix commented on GitHub (Jul 14, 2020): Hmm I see that this issue is a year old, but I still have the same issue with emacs in CentOS 7.8 ssh'ed in from Windows Terminal. When googling I found a thread for another console/terminal program ConEmu which had a similar issue with emacs: https://github.com/Maximus5/ConEmu/issues/1691 The top comment there seems to have some more detailed information about what the reason could be. Does that help in getting the issue fixed for Windows Terminal?
claunia commented 2026-01-30 21:46:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 22, 2022):

Hey this issue is... pretty dang old at this point. Anyone still seeing this? I reckon this is probably due to an input sequence getting chopped in half and not getting written to the console in a single write. Can we get a fresh repro here with a specific ssh version (and distribution)/?

@zadjii-msft commented on GitHub (Aug 22, 2022): Hey this issue is... pretty dang old at this point. Anyone still seeing this? I reckon this is probably due to an input sequence getting chopped in half and not getting written to the console in a single write. Can we get a fresh repro here with a specific ssh version (and distribution)/?
claunia commented 2026-01-30 21:46:55 +00:00
Author
Owner
Copy Link

@Hyper200 commented on GitHub (Aug 22, 2022):

i haven't had it since i switch to:
https://github.com/microsoft/terminal/issues/173#issuecomment-388091934

Thanks,

@Hyper200 commented on GitHub (Aug 22, 2022): i haven't had it since i switch to: https://github.com/microsoft/terminal/issues/173#issuecomment-388091934 Thanks,
claunia commented 2026-01-30 21:46:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 22, 2022):

That's kinda weird tbh, cause typically the Windows Console & Terminal should work with xterm-256color. I suppose your issue is sorted out, and we can just close this out for now. If something else like this comes up, we can track it in a fresh issue rather than this fairly stale one.

Thanks!

@zadjii-msft commented on GitHub (Aug 22, 2022): That's kinda weird tbh, cause typically the Windows Console & Terminal _should_ work with `xterm-256color`. I suppose your issue is sorted out, and we can just close this out for now. If something else like this comes up, we can track it in a fresh issue rather than this fairly stale one. Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Output Area-Rendering Help Wanted Issue-Bug Needs-Attention Needs-Tag-Fix Product-Conhost Resolution-No-Repro
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#251
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?