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

Cannot use AltGr+u with U.S. International keyboard #37002

Closed
GeorgeHernandez opened this issue Oct 26, 2017 · 5 comments
Closed

Cannot use AltGr+u with U.S. International keyboard #37002

GeorgeHernandez opened this issue Oct 26, 2017 · 5 comments
Assignees
Labels
*caused-by-extension Issue identified to be caused by an extension

Comments

@GeorgeHernandez
Copy link

  • VSCode Version: Code 1.17.2 (b813d12, 2017-10-16T13:59:46.104Z)
  • OS Version: Windows_NT x64 10.0.15063
  • Extensions:
Extension Author (truncated) Version
yaml ada 0.0.9
Bookmarks ale 0.17.0
alignment ann 0.3.0
vscode-markdownlint Dav 0.11.0
vscode-eslint dba 1.4.0
githistory don 0.2.3
ftp-sync luk 0.3.3
mssql ms- 1.2.0
csharp ms- 1.12.1
java red 0.12.0
code-spell-checker str 1.4.10
json2yaml tux 0.2.0
vscode-java-debug vsc 0.2.0

Steps to Reproduce:

  1. Turn on U.S. International keyboard in Windows.
  2. Open file in Visual Studio Code.
  3. Type AltGr+u

Reproduces without extensions: No

Issue does NOT occur without extensions. However searching keybindings for Alt+u does not find anything.

Issue does NOT occur for the other Spanish characters (¡¿ÁáÉéÍíÑñÓóÚÜü), just ú when entered as AltGr+u.

Issue does NOT occur when entering ú via '+u.

@dbaeumer
Copy link
Member

@alexandrudima do you have an idea why this could happen even if no extension defines the short cut.

@GeorgeHernandez can you check the contribution for each of your extensions to see whether they do define such a short cut. And can you selectively disable ( can be done in the extension viewlet) the extensions to see if we can find the extension that causes the problem

capture

capture

@dbaeumer dbaeumer added the info-needed Issue requires more information from poster label Oct 26, 2017
@dbaeumer dbaeumer reopened this Oct 26, 2017
@GeorgeHernandez
Copy link
Author

TLDNR: I've isolated it to the "Language Support for Java(TM by Red Hat" extension, but cannot be sure about the "Debugger for Java" extension.

Given [all, debug, java] where:

  • all: Enabled status of all extensions except for the Debug and Java extensions.
  • debug: Enabled status of the "Debugger for Java" extension.
  • java: Enabled status of the "Language Support for Java" extension.

I have tested the permutations for the issue:

  • [0,0,0] -> No
  • [0,0,1] -> Yes
  • [0,1,0] -> N/A. The Debugger is dependent on the Java extension.
  • [0,1,1] -> Y
  • [1,0,0] -> N
  • [1,0,1] -> Y
  • [1,1,0] -> N/A. The Debugger is dependent on the Java extension.
  • [1,1,1] -> Y

As you can see it only happens when the Java extension is on. Since the Debugger extension is dependent on the Java extension, I could not determine if the former would also cause the issue if the Java extension were fixed.

@dbaeumer dbaeumer removed the info-needed Issue requires more information from poster label Oct 30, 2017
@alexdima
Copy link
Member

alexdima commented Oct 30, 2017

This is indeed caused by redhat.java. From their package.json:

 "keybindings": [
      {
        "command": "java.projectConfiguration.update",
        "key": "ctrl+alt+u",
        "mac": "cmd+alt+u",
        "when": "editorFocus"
      } 

@GeorgeHernandez I wonder why ctrl+alt+u did not show up when you searched for alt+u. Did you use the keybindings UI for searching or did you open the keybindings.json. Both should have shown in this case the ctrl+alt+u binding when searching for alt+u.

P.S. AltGr == Ctrl+Alt+

@dbaeumer
Copy link
Member

@aeschli do you have an idea.

@GeorgeHernandez please file the issue against the vscode java extension GitHub repository.

@aeschli
Copy link
Contributor

aeschli commented Oct 30, 2017

This issue was moved to redhat-developer/vscode-java#348

@aeschli aeschli closed this as completed Oct 30, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 14, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*caused-by-extension Issue identified to be caused by an extension
Projects
None yet
Development

No branches or pull requests

4 participants