Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support instant visibility of characters over high latency SSH connections #8490

Closed
gakio12 opened this issue Dec 4, 2020 · 2 comments
Closed
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@gakio12
Copy link

gakio12 commented Dec 4, 2020

Description of the new feature/enhancement

In the later versions of VSCode, the terminal has a feature where the text you type will show up immediately as a slightly greyer font and will become the standard color when the remote SSH server calls back confirming the key press. This makes working on servers across the globe much better. Unfortunately I don't have the specific commit to VSCode's terminal to enable this, but I was hoping we could get this implemented in Windows Terminal as well.

For example, the following sequence is painful over a connection with 500 ms latency:

"foodis good" -> press right arrow key until between food and is -> " "

In the latest VSCode terminal, this all shows up as if it is being typed on a local running terminal as a slightly greyer font, and the font slowly turns the correct color as the remote server calls back. Basically the only time the user is waiting for the remote callback is when pressing a key that needs a response, such as TAB or ENTER.

@gakio12 gakio12 added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Dec 4, 2020
@ghost ghost added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Dec 4, 2020
@DHowett
Copy link
Member

DHowett commented Dec 4, 2020

Thanks for the request! This is a /duplicate of #8178.

@ghost
Copy link

ghost commented Dec 4, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Dec 4, 2020
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Dec 4, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants