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

Shortcut ctrl+` fail after reactivate vscode window #82667

Closed
illava opened this issue Oct 16, 2019 · 6 comments
Closed

Shortcut ctrl+` fail after reactivate vscode window #82667

illava opened this issue Oct 16, 2019 · 6 comments
Assignees
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code) windows VS Code on Windows issues

Comments

@illava
Copy link

illava commented Oct 16, 2019

Issue Type: Bug
File on: Visual Studio Code

Reproduce steps

  1. Open vscode
  2. now deactivate vscode window (switch to other program) and activate vscode window again.

Actual

  • Ctrl + ` no responce, not open nor close terminal
  • In Preference-->Keyboard Shortcuts-->Record Keys, when recording shortcut "Ctrl + `", "Ctrl + " appear and not seaching

Expacted

  • Ctrl + ` works fine, open terminal and close
  • In Preference-->Keyboard Shortcuts-->Record Keys, when recording "Ctrl + `", "ctrl+oem_3" should appear and begin to search

VS Code version: Code 1.39.2 (6ab5985, 2019-10-15T15:35:18.241Z)
OS version: Windows_NT x64 10.0.18362

System Info
Item Value
CPUs Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 x 1800)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
oop_rasterization: disabled_off
protected_video_decode: enabled
rasterization: enabled
skia_deferred_display_list: disabled_off
skia_renderer: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 7.81GB (2.52GB free)
Process Argv
Screen Reader no
VM 0%
Extensions: none
@vijayksingh
Copy link

Not able to create the bug. Can you verify the steps again, anything you have done before you got the issue?

With the steps, you mentioned to reproduce, the bug is not happening.

@illava
Copy link
Author

illava commented Oct 16, 2019

I can reproduce it both office PC and home.

  1. Open vscode, a file is already open(test.cu or Untitled-1).
  2. (Option) Check ctrl + ` works fine(open and close terminal)
    3.. switch to other window and reopen vscode window
  3. Ctrl + ` not response.

Funny that

  1. Open vscode with Default page(show all cmd, open file, etc.).
  2. switch to other window and reopen vscode window
  3. ctrl + ` response once(open terminal once).

Switch to any windows is reproducing. I tried chrome, windows setting panel, etc.

@alexdima alexdima added the windows VS Code on Windows issues label Oct 17, 2019
@alexdima
Copy link
Member

@illava I cannot reproduce. ctrl+` works reliably for me, even if I focus another application and return to VS Code later. Do you happen to use a specific keyboard layout where this reproduces?

@alexdima alexdima added the info-needed Issue requires more information from poster label Oct 17, 2019
@illava
Copy link
Author

illava commented Oct 18, 2019

I figure out the issue is related to IME(QQPinyin). Repaired after uninstalling.
Thanks for your help.

@illava
Copy link
Author

illava commented Oct 18, 2019

That‘s why it appears only my home and office PC.
Don't know what's the exact problem with IME. Since it is rare used and lacks feedback methods. Simply change to another IME will be fine.

@vscodebot vscodebot bot removed the new release label Oct 20, 2019
@alexdima
Copy link
Member

Ok, it seems that you have a similar issue as #70482 . ctrl+` is simply reserved and used by the IME, therefore the keybinding does not reach VS Code.

@alexdima alexdima added upstream Issue identified as 'upstream' component related (exists outside of VS Code) and removed info-needed Issue requires more information from poster labels Oct 21, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
upstream Issue identified as 'upstream' component related (exists outside of VS Code) windows VS Code on Windows issues
Projects
None yet
Development

No branches or pull requests

3 participants