-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Alt + F not triggering "File menu" #10525
Comments
@jjacode I cannot reproduce on my Windows 10, sorry. |
@jjacode could you give our insider release a try to see if this issue is fixed? |
Cannot reproduce in VS Code 1.5.3 on Windows 10 either. Removing the "bug" label". @jjacode let us know if you still face issues |
This only appears to be reproducible when the integrated terminal has focus. |
I think the integrated terminal steals all keypresses. @Tyriar can comment on that. |
@jjacode the terminal consumes most keypresses with the exception of the commands listed in the |
@Tyriar I've not tried it in Linux yet. But, in Windows when I press Alt the File Menu does the underlining like expected (File underlines "f", Edit underlines "E", etc). But then the terminal captures the letter. EDIT: I just updated VS Code to 1.5.3, and the issue remains. I'm still in Windows 10. |
Do you press alt and then f, not alt+f at the same time? I think that's an Electron thing. |
I'm pressing and holding Alt, then with Alt still pressed I press "F" Alt+f at the same time. |
Repro'd on Windows, xterm.js must be consuming the keystrokes for some reason. |
I also have the same problem, all menu will not popup when hitting alt + f / e / v / g / h
|
I've just started having this issue today. Was working fine yesterday, and the last update was a week ago so it's been working fine for some days until now. VSCode 1.7.2 Edit: worked again after restarting Windows |
Created an upstream issue xtermjs/xterm.js#384 |
Upstream doesn't want this for good reason. Should check what powershell, cmd, cmder, etc. do with their alt+shortcuts/menus and see if we need a flexible solution, a on/off setting or maybe we can just hardcode them. |
Closing since this is as designed upstream, see xtermjs/xterm.js#384 |
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: