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

Local Echo: Predict the display of remote characters #11295

New Issue
Open
opened 2026-01-31 02:43:39 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 02:43:39 +00:00
Owner
Copy Link

Originally created by @MarnoRossouwX on GitHub (Nov 6, 2020).

Description of the new feature/enhancement

Predict characters that will be displayed in the terminal without having to wait for the shell. This is done in the 1.51 release of Visual Studio Code and is explained in detail on its release notes: https://code.visualstudio.com/updates/v1_51#_local-echo

As explained in the Visual Studio Code release notes, this will be particularly useful when working over an ssh connection.

Proposed technical implementation details (optional)

Originally created by @MarnoRossouwX on GitHub (Nov 6, 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! --> # Description of the new feature/enhancement Predict characters that will be displayed in the terminal without having to wait for the shell. This is done in the 1.51 release of Visual Studio Code and is explained in detail on its release notes: [https://code.visualstudio.com/updates/v1_51\#_local-echo](https://code.visualstudio.com/updates/v1_51\#_local-echo) As explained in the Visual Studio Code release notes, this will be particularly useful when working over an ssh connection. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureArea-OutputProduct-Terminal labels 2026-01-31 02:43:39 +00:00
claunia commented 2026-01-31 02:43:40 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Nov 8, 2020):

Well that's certainly an interesting idea. There's a little more discussion here. Specifically that calls out not doing this in the alt buffer, which I think is a reasobaly assumption.

From purely an implementation standpoint, I wonder if there's an easy way to do this with "overlays" like we had considered years ago for popups. I'm not sure that we'd want to actually populate the buffer with these "predicted" contents, we'd need some way to keep the predictions separate.

@zadjii-msft commented on GitHub (Nov 8, 2020): Well that's certainly an interesting idea. There's a little more discussion [here](https://www.reddit.com/r/programming/comments/jp25ks/visual_studio_code_october_2020/gbcaawg/). Specifically that calls out _not_ doing this in the alt buffer, which I think is a reasobaly assumption. From purely an implementation standpoint, I wonder if there's an easy way to do this with "overlays" like we had considered years ago for popups. I'm not sure that we'd want to actually populate the buffer with these "predicted" contents, we'd need some way to keep the predictions separate.
claunia commented 2026-01-31 02:43:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Dec 4, 2020):

This sounds a lot like mosh.

@DHowett commented on GitHub (Dec 4, 2020): This sounds a lot like `mosh`.
claunia commented 2026-01-31 02:43:40 +00:00
Author
Owner
Copy Link

@djsavvy commented on GitHub (Dec 7, 2020):

Does this really need to be implemented in the terminal itself? I feel like delegating this functionality to mosh makes more sense.

@djsavvy commented on GitHub (Dec 7, 2020): Does this really need to be implemented in the terminal itself? I feel like delegating this functionality to `mosh` makes more sense.
claunia commented 2026-01-31 02:43:40 +00:00
Author
Owner
Copy Link

@gakio12 commented on GitHub (Dec 10, 2020):

mosh requires a server component to be installed. The functionality in VSCode does not require a remote component.

@gakio12 commented on GitHub (Dec 10, 2020): `mosh` requires a server component to be installed. The functionality in VSCode does not require a remote component.
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 Issue-Feature Product-Terminal
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#11295
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?