From @prenetic on August 16, 2017 17:56

• VSCode Version: 1.15.0
• OS Version: Windows 10 version 1703 (build 15053.540)
• Visual Studio Keymap Version: 0.1.7

Steps to Reproduce:

1. Install Visual Studio Keymap extension and reload.
2. Open an editor with any non-empty text file.
3. Place the cursor somewhere in the middle of the text file (remember where) to observe behavior.
4. Select the Source Control tab.
5. Begin typing a commit message (does not matter if file belongs to a repository or not), and then press Ctrl+Backspace to delete a word to the left of the cursor within the commit message.
6. Observe that the open file is now dirty and the word to the left of where the cursor in the main editor was placed in step 2 is now missing.
7. In the same commit message, press Ctrl+Delete to delete a word to the right of the cursor within the commit message.
8. Observe that the word to the right of the cursor in the main editor is now missing.

Reproduces without extensions: No

Copied from original issue: microsoft/vscode#32651

Hi there!

I'm reaching out to you because we currently have your extension manually added to our extension gallery at Coder for code-server, and we're currently working on a migration to open-vsx, which is also used by other community VSCode forks (including, but not limited to Arch Linux's Code-OSS builds and VSCodium).

We (and other open source VSCode forks) cannot use Microsoft's extension gallery, as MS' terms of service allows only the proprietary MS products to interact with the official gallery.

We'd really appreciate it if you can add your extension to open-vsx! A simple guide on publishing extensions to Open-VSX is available here.

• VSCode Version: Code 1.16.1 (27492b6bf3acb0775d82d2f87b25a93490673c6d, 2017-09-14T16:38:23.027Z)
• OS Version: Windows_NT x64 6.1.7601
• Extensions:

After hitting another keyboard shortcut conflict I thought I'd do an exhaustive search for more so I've prepared a spreadsheet that highlights duplicate keyboard mapping to assist in the hunt. Below is an attached Excel sheet that I produced using the steps above to help identify keyboard conflicts and the procedure I used to create this list.

I also found some cases where an identical mapping rule was duplicated which might cause problems with your code maintenance in the future.

Here the conflict that trigged my search:

• "ctrl+shift+g" conflict: "Show SCM" and "workbench.action.files.openFileFolder"

Steps to Reproduce:

1. "Open Keybaord Shortcuts"
2. Edit "keybinding.json"
3. Select ALL (Ctrl-A) and Copy (Ctrl-C)
4. Visit https://konklone.io/json/ to convert JSON to CSV
   • Remove header comment (1 line) before "[" and and all trailing comments after last "]"
5. Download keyboard shortcuts as a CSV file.
6. Open in Excel and sort by 1st column ("key")
7. Use conditional formatting to highlight duplicate key mappings (1st column)
   • Example: http://www.excel-easy.com/examples/find-duplicates.html

Inspect to check for duplicate key mappings that may conflict. I fully understand that you'd need to check the "when" condition. Since we sorted the rules, this sheet does not record the original rule order which may also affect their interpretation. I'm not up on this but I'm assuming you are!

Happy conflict hunting 👍

vscode-keyboard-conflict.xlsx

Hello Team,

This is just a note that installing VS Code Keymap breaks the Toggle Sidebar (Control + B) Shortcut.

I have downloaed this extension but It does not seem to work. eg. Ctrl E + ctrl D in vs 2017 formats the document. Here it's not working.

See microsoft/vscode#47487 which claims that in Visual Studio the cursor is kept visible when using ctrl+up and ctrl+down. This can be achieved via the keybindings:

    {
        "key": "ctrl+down",
        "command": "editorScroll",
        "args": {
            "to": "down",
            "by": "line",
            "revealCursor": true
        }
    },
    {
        "key": "ctrl+up",
        "command": "editorScroll",
        "args": {
            "to": "up",
            "by": "line",
            "revealCursor": true
        }
    }

Can you also provide invert of this mapping?
I'm looking for Visual Studio Code Keymap for Visual Studio.

Some of VS code shortcuts are great like Alt+ ← / → Go back / forward.

I tried to install the Visual Studio Keymap expecting to get the same shortcuts as I'm used on Visual Studio 2015.

I don't know if I did something wrong but it's been really hard for me using the editor and learning all over again the shortcuts.

I now I can remap them but to remember them all is a pain in the neck.

If this extensions is not for that. Does anybody have already mapped the shortcuts to be similar to the ones from VS2015?

Thanks

The Terminal clear Ctlr+K not working after installing Visual studio keymap Extension

"You can see all the keyboard shortcuts in the extension's contribution list."

What does this mean? I cannot find it.

Please provide a straight-forward, easy-to-find, direct link on the main page of this extension to a list (such as markdown or pdf) of the replacement keyboard shortcuts this extension supplies.

In Visual Studio Code. Shift Tab "Outdents" the selected line. In Visual Studio it "Untabs" (removes tab/x spaces from current caret position)
I couldn't see a command to change this to, but would love it if someone could work it out!

I can use the combination in Visual Studio. However I can't in VS Code.

Visual Studio editor implements a very useful feature that can be used to efficiently navigate through code. It would be nice to have it supported in Visual Studio code. Thank you.

Hi
On Windows use Ctrl+C to copy, but on Mac, use command+C. If i set modifier keys in System preferences "Control to Command" and "Command to Control", Now The left bottom button + C is copy. Same usage habits as Windows.
But if I install Visual Studio Keymap, the shortcut of system and the shortcut of vs Code Meaning will not be the same, It can't be like using the shortcut keys on windows.
Is there a way to detect whether the modifier keys of the macOS system have been modified, or add an option to be selected by the user.
Thanks

1. Have a file open in the editor where the cursor is not at the start of the document (e.g. a Typescript file)
2. Open the "Quick open" (Ctrl+,)
3. Type in some keyword to find a file (don't hit enter)
4. Hit Ctrl+backspace to remove the keyword just entered
5. See that instead of the keyword being removed, some content before the cursor in the editor was removed.

ctrl+space in VS is a shortcut to Intellisense, or as VSCode calls it, triggerSuggest. Why is this extension remapping it to deleteWordStartLeft?

After installing this extension I can't type polish characters "ó" (right alt+O) and "ł" (right alt+L).
This is because of the new shortcuts:

package.json line 104:
{
"key": "ctrl+alt+o",
"command": "workbench.action.output.toggleOutput"
},
{
"key": "ctrl+alt+l",
"command": "workbench.view.explorer"
},

editor.action.smartSelect.grow is mapped to Shift + Alt + RightArrow.

However, this doesn't work. It is supposed to select the word on first use, then the line, then the code block and then keep selecting larger code blocks.

On the page https://marketplace.visualstudio.com/items?itemName=ms-vscode.vs-keybindings&ssr=false#overview There is Preview tag for the extension.
But the extension looks quite mature- more than 3 years and 230,594 installs.

Should you remove the tag? It will give more confidence for new users to install it.

I'm very used to this shortcut in Visual Studio. I've made the customization myself, but I would guess it would be nice to have it as a default for this extension.

The closeEditor and closeWindow shortcuts are bound to ctrl+w and they do not work after installation of the extension.

When editing text fields in Extensions / Source control, when CMD+Backspace or CMD+Delete is pressed, keybinding commands fired in the text editor.

This is not the kind of behavior i expect nor i want / need. I will create a pull request to address this issue soon.

See microsoft/vscode#30086.

From @ItWorksOnMyMachine on June 24, 2017 18:10

• VSCode Version: Code 1.13.1 (379d2efb5539b09112c793d3d9a413017d736f89, 2017-06-14T18:21:47.485Z)
• OS Version: Windows_NT ia32 10.0.15063
• Extensions:

I pasted method into the editor but the formatting was off and there were too many spaces before the method name. I used Ctrl+Home to return to the beginning of the line and the pressed Ctrl+Delete with the intention of deleting all whitespace and then pressing my tab key to indent. Unfortunately, the Ctrl+Delete deleted all the whitespace and the method name. I would expect it to delete all whitespace up to, but not including, the method name.
Steps to Reproduce:

Copied from original issue: microsoft/vscode#29385

In Visual Studio, the "Quick Actions" shortcut is Alt+Enter.

In Visual Studio Code, the default key mapping for "Show Fixes", the equivalent function, is Ctrl+..

It would be good if Alt+Enter behaved the same way in VS Code and VS.

There appear to be two other mappings for Alt+Enter; "open breakpoints to the side" and "select all matches". I think these are not as important and can probably be removed (although I think the "when" condition is different as "Show Fixes" is when there is problemFocus).

• VSCode Version: 1.31.1 (1.31.1)
• OS Version: Any

Steps to Reproduce:

1. Install Visual Studio Keymap extension
2. Write line like "__________________first second".
3. Set caret at first char in this line.
4. Push [ctrl + del] shortcut.
5. Expected result "first second" but it " second".

test line:

after [ctrl+del]:

expected result:

hello, so in microsoft visual studio when i write in C lang, i was able to move to next things on the line with tab.
i dont know how to explain it right, but here if i press tab its doing tab space.
i have search for the key name and its: Edit.SelectNextControl
i dont have it in your keyboard option.
how i can change it to be Edit.SelectNextControl and not tab space?
thank

Extracted from microsoft/vscode#29327 (comment)

From @tohagan

In VSCode 1.16.1 I found that there is a keyboard mapping conflict for Shift-Alt-Down:

• Copy Line Down (wanted)
• cursorColumnSelectDown (not wanted)

Further I found that ALL the cursorColumnSelect* functions have multple keyboard mappings are creating more keyboard shortcut conflicts.

Hi, thanks for this extension. I note that Ctrl+L doesn't do quite the same thing as on Visual Studio. There, with nothing selected, it cuts the current line with cr-lf and moves the cursor to the start of the line, and with text selected it it acts like Ctrl+X. I only use it with no selection.

My understanding (drawing on this vscode feature request) is that one would need to define a new command in the extension to call other commands conditionally.

Hi,

I just wonder if there is anyone active maintaining this extension at the moment?
Can I offer some help?

I think this is a very valuable extension and there are many active users. So this should get some care.

I don't want to complain but liked to offer my help.

Greetings
KirK

From @adison on September 30, 2017 6:57

• VSCode Version: Code 1.16.1 (27492b6bf3acb0775d82d2f87b25a93490673c6d, 2017-09-14T16:24:39.530Z)
• OS Version: Darwin x64 16.7.0
• Extensions:

Steps to Reproduce:

1. use alt + arrow key(left/right) to jump word by word
2. use shift to select anything(word or letter) and try alt + arrow(right/left) again, it can only move letter by letter.

Reproduces without extensions: Yes

Without this feature, it's hard to delete multiple words efficiently.

Copied from original issue: microsoft/vscode#35412

The description of this repository tells me that it has moved to https://github.com/Microsoft/vscode-vs-keybindings

However the comments for submitting a missing shortcut direct me to https://github.com/rebornix/vscode-vs-keybindings who is correct? It looks like there was a pull request recently on the new site microsoft/vscode-vs-keybindings#16 but that just hasn't pushed in?

By default, the Rename Symbol refactoring is mapped to F2 in Code, but in VS 2015/17 it's mapped to Ctrl+R, Ctrl+R. This throws my muscle memory way off and this extension doesn't have the mapping yet.