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

Its not possible to send all control codes to the terminal window. #48950

Closed
pjs102 opened this issue Apr 30, 2018 · 3 comments
Closed

Its not possible to send all control codes to the terminal window. #48950

pjs102 opened this issue Apr 30, 2018 · 3 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster terminal General terminal issues that don't fall under another label windows VS Code on Windows issues

Comments

@pjs102
Copy link

pjs102 commented Apr 30, 2018

Issue Type: Bug

Its not possible to send all control codes to the terminal window. When running an ssh session to a linux box, clicking Ctrl-S will pause the screen, but you are unable to send in Ctrl+Q to resume the session.

VS Code version: Code 1.22.2 (3aeede7, 2018-04-12T16:38:45.278Z)
OS version: Windows_NT x64 10.0.16299

Extensions (9)
Extension Author (truncated) Version
solargraph cas 0.16.0
vscode-markdownlint Dav 0.15.0
cpptools ms- 0.16.1
Ruby reb 0.18.0
java red 0.23.0
vscode-java-debug vsc 0.9.0
vscode-java-pack vsc 0.3.0
vscode-java-test vsc 0.5.0
vscode-maven vsc 0.7.0
@vscodebot vscodebot bot added the terminal General terminal issues that don't fall under another label label Apr 30, 2018
@Tyriar
Copy link
Member

Tyriar commented Apr 30, 2018

@pjs102 are you using WSL bash?

@Tyriar Tyriar added info-needed Issue requires more information from poster windows VS Code on Windows issues labels Apr 30, 2018
@pjs102
Copy link
Author

pjs102 commented May 1, 2018

I'm running Windows powershell. From there i'm launching "vagrant ssh" to a virtual machine.

@Tyriar
Copy link
Member

Tyriar commented May 1, 2018

I'm guessing the problem is one of the following then:

@Tyriar Tyriar closed this as completed May 1, 2018
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label May 1, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Jun 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) info-needed Issue requires more information from poster terminal General terminal issues that don't fall under another label windows VS Code on Windows issues
Projects
None yet
Development

No branches or pull requests

2 participants