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

Keyboard does not work #7823

Closed
NeiderCamargo opened this issue Oct 4, 2020 · 5 comments
Closed

Keyboard does not work #7823

NeiderCamargo opened this issue Oct 4, 2020 · 5 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@NeiderCamargo
Copy link

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

Any other software?

Steps to reproduce

Expected behavior

Actual behavior
@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 Oct 4, 2020
@zadjii-msft
Copy link
Member

@DeveloperNfk By any chance, have you disabled the "Touch keyboard and handwriting service"? See #4448

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

ghost commented Oct 9, 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.

@benfavre
Copy link

Have had this issue for a while ... what's the point of this repo/project if you don't test keyboard support ?

@ghost ghost removed the No-Recent-Activity This issue/PR is going stale and may be auto-closed without further activity. label Oct 10, 2020
@DHowett
Copy link
Member

DHowett commented Oct 10, 2020

@benfavre instead of reading the linked issue or applying critical thinking about the question earlier in the thread, you’ve decided that for the entire year or more that terminal has existed nobody has tested KEYBOARD SUPPORT? Come now.

@microsoft microsoft locked as resolved and limited conversation to collaborators Oct 10, 2020
@DHowett
Copy link
Member

DHowett commented Oct 10, 2020

/dup #4448

@ghost ghost closed this as completed Oct 10, 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 Needs-Author-Feedback The original author of the issue/PR needs to come back and respond to something labels Oct 10, 2020
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@DHowett @benfavre @zadjii-msft @NeiderCamargo