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.

Sign up for GitHub

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

Jump to bottom

Characters stay present on terminal but disappear from command when using backspace #4537

Closed
BenConstable9 opened this issue Feb 11, 2020 · 2 comments
Closed

Characters stay present on terminal but disappear from command when using backspace #4537

BenConstable9 opened this issue Feb 11, 2020 · 2 comments
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something 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 No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.

Comments

@BenConstable9
Copy link
Contributor

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.592]
Windows Terminal version (if applicable): 0.8.10261.0

Steps to reproduce

Hard to reproduce as only occasionally happens.

Expected behavior

The characters should be deleted from the input command.

Actual behavior

When backspacing after typing an input command, characters stay in the command input but do not seem to affect the command. Rogue characters (normally the first character of the previous command typed), will linger on the UI but do not appear to have any effect on a command typed afterwards.
@ghost ghost added 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 Feb 11, 2020
@DHowett-MSFT
Copy link
Contributor

This may have been fixed by #4403. Can you try to confirm when 0.9 comes out (tomorrowish?)

@DHowett-MSFT DHowett-MSFT added the Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something label Feb 13, 2020
@ghost ghost added the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Feb 17, 2020
@ghost
Copy link

ghost commented Feb 17, 2020

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 ghost closed this as completed Feb 21, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something 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 No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DHowett-MSFT @BenConstable9