Skip to content

Commit 14bf642

Browse files
Merge pull request #4124 from MicrosoftDocs/main638451767475298561sync_temp
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
2 parents dd274fb + dfeccbb commit 14bf642

File tree

1 file changed

+25
-1
lines changed

1 file changed

+25
-1
lines changed

hub/powertoys/keyboard-manager.md

Lines changed: 25 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,17 @@ There are a few rules to follow when remapping shortcuts. These rules only apply
9999

100100
- Shortcuts must begin with a modifier key: <kbd>Ctrl</kbd>, <kbd>Shift</kbd>, <kbd>Alt</kbd>, or <kbd>⊞ Win</kbd>
101101
- Shortcuts must end with an action key (all non-modifier keys): A, B, C, 1, 2, 3, etc.
102-
- Shortcuts cannot be longer than four keys
102+
- Shortcuts cannot exceed four keys in length, or five if the shortcut is a 'chord'.
103+
104+
#### Shortcuts with chords
105+
Shortcuts can be created with one or more modifiers and two non-modifier keys. These are called 'chords.' In order to create a chord, you need to use the edit button to open the modal to record the shortcut using the keyboard. Once this is open, you need to toggle on the 'Allow chords' switch. Doing this allows you to enter two non-modifier keys. For example, you can create shortcuts using a chord based on 'V' for **V**olume **U**p and **V**olume **D**own like this::
106+
| Select: | To send: |
107+
| :--- | :--- |
108+
| `Shirt`+`Ctrl` + `V` , `U` | `Volume Up` |
109+
| `Shirt`+`Ctrl` + `V` , `D` | `Volume Down` |
110+
111+
Chords are handy if you have a number of shortcuts that are similar, and so it makes sense to have them all start with the same non-modifier key.
112+
103113

104114
### Remap a shortcut to a single key
105115

@@ -122,6 +132,20 @@ For example, to replace the shortcut <kbd>Ctrl</kbd>+<kbd>G</kbd> with `Hello!`
122132
| :--- | :--- |
123133
| `Ctrl` + `G` | `Hello!` |
124134

135+
### Remap a shortcut to start an app
136+
Keyboard Manager enables you to start applications with the activation of any shortcut. Select "Start App" from the action in the "To:" column to do this. There are a few options to configure when using this type of shortcut. They are:
137+
| Option | Meaning |
138+
| :--- | :--- |
139+
| App | This is the path to an executable. Environment variables will be expanded. |
140+
| Args | Arguments that will be sent to the app. |
141+
| Start in | The working directory for the app to start in. |
142+
| Elevation | Specify the elevation level to start the app. The options include Normal, Elevated, and Different User. |
143+
| If running | What action should be taken when this shortcut is activated while the app is already running? The options are: Show Window, Start another instance, Do nothing, Close, End task. |
144+
| Visibility | Specifies whether the app will be visible. This is useful when the app is a console or something you don't want to see. |
145+
146+
### Remap a shortcut to open a URI
147+
This type of shortcut action will open a URI. The only option is the actual Path/URI. Almost anything you can issue on the command line should work. See [Launch an app with a URI](/windows/uwp/launch-resume/launch-app-with-uri) for more examples.
148+
125149
### App-specific shortcuts
126150

127151
Keyboard Manager enables you to remap shortcuts for only specific apps (rather than globally across Windows).

0 commit comments

Comments
 (0)