starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Binding 'paste' to shift+insert doesn't work #2502

New Issue
Closed
opened 2026-01-30 22:56:53 +00:00 by claunia · 13 comments
claunia commented 2026-01-30 22:56:53 +00:00
Owner
Copy Link

Originally created by @easeev on GitHub (Jul 3, 2019).

Environment

Windows build number: 10.0.18922.1000
Windows Terminal version (if applicable): 0.2.1715.0

Steps to reproduce

Add the following to the keybindings section of profiles.json:

{
	"command" : "paste",
	"keys" : 
	[
		"shift+insert"
	]
},

Expected behavior

Text is pasted once I press Shift+Insert. I'm on WSL terminal.

Actual behavior

Nothing happens. If the binding is disabled, I get 2~ when this key combination is pressed.

Reference: https://github.com/microsoft/terminal/issues/112#issuecomment-507822964

Originally created by @easeev on GitHub (Jul 3, 2019). <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: 10.0.18922.1000 Windows Terminal version (if applicable): 0.2.1715.0 ``` # Steps to reproduce Add the following to the `keybindings` section of `profiles.json`: ``` { "command" : "paste", "keys" : [ "shift+insert" ] }, ``` # Expected behavior Text is pasted once I press Shift+Insert. I'm on WSL terminal. # Actual behavior Nothing happens. If the binding is disabled, I get `2~` when this key combination is pressed. Reference: https://github.com/microsoft/terminal/issues/112#issuecomment-507822964
claunia added the Resolution-Duplicate label 2026-01-30 22:56:53 +00:00
claunia commented 2026-01-30 22:56:54 +00:00
Author
Owner
Copy Link

@bronthulke commented on GitHub (Jul 3, 2019):

I've also tried to bind "paste" to ctrl+v and that didn't work either - perhaps is the "paste" keybinding command not set up to work at all?

@bronthulke commented on GitHub (Jul 3, 2019): I've also tried to bind "paste" to ctrl+v and that didn't work either - perhaps is the "paste" keybinding command not set up to work at all?
claunia commented 2026-01-30 22:56:54 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 3, 2019):

Not in 0.2.1715.0!

@DHowett-MSFT commented on GitHub (Jul 3, 2019): Not in 0.2.1715.0!
claunia commented 2026-01-30 22:56:54 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 3, 2019):

#1093

@DHowett-MSFT commented on GitHub (Jul 3, 2019): #1093
claunia commented 2026-01-30 22:56:54 +00:00
Author
Owner
Copy Link

@easeev commented on GitHub (Jul 3, 2019):

Looking forward for Microsoft Store update!

@easeev commented on GitHub (Jul 3, 2019): Looking forward for Microsoft Store update!
claunia commented 2026-01-30 22:56:54 +00:00
Author
Owner
Copy Link

@sandric commented on GitHub (Jul 5, 2019):

Hmm, mine version is 0.2.1831.0, and I still have no luck making such shortcut working, should this work?

@sandric commented on GitHub (Jul 5, 2019): Hmm, mine version is 0.2.1831.0, and I still have no luck making such shortcut working, should this work?
claunia commented 2026-01-30 22:56:55 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 5, 2019):

Not in 0.2.1831.0.

@DHowett-MSFT commented on GitHub (Jul 5, 2019): Not in 0.2.1831.0.
claunia commented 2026-01-30 22:56:55 +00:00
Author
Owner
Copy Link

@bronthulke commented on GitHub (Jul 5, 2019):

I think there's some confusion here @DHowett-MSFT - when you simply say "Not in 0.2.1715.0!" do you mean that it's no longer an issue in 0.2.1715.0? As that is what I thought, and it implies that it would also be fixed in 0.2.1831.0 as @sandric is experiencing. A few extra words may assist in our understanding :)

@bronthulke commented on GitHub (Jul 5, 2019): I think there's some confusion here @DHowett-MSFT - when you simply say "Not in 0.2.1715.0!" do you mean that it's no longer an issue in 0.2.1715.0? As that is what I thought, and it implies that it would also be fixed in 0.2.1831.0 as @sandric is experiencing. A few extra words may assist in our understanding :)
claunia commented 2026-01-30 22:56:55 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jul 5, 2019):

Hey, sorry! These key bindings didn’t make it into the 0.2 release (neither the original release nor the servicing release). It will come out with the 0.3 preview release. Thanks!

@DHowett-MSFT commented on GitHub (Jul 5, 2019): Hey, sorry! These key bindings didn’t make it into the 0.2 release (neither the original release nor the servicing release). It will come out with the 0.3 preview release. Thanks!
claunia commented 2026-01-30 22:56:55 +00:00
Author
Owner
Copy Link

@bronthulke commented on GitHub (Jul 5, 2019):

Awesome, thanks for clarifying!

@bronthulke commented on GitHub (Jul 5, 2019): Awesome, thanks for clarifying!
claunia commented 2026-01-30 22:56:55 +00:00
Author
Owner
Copy Link

@tovine commented on GitHub (Nov 22, 2019):

This still doesn't work for me... Except for in PowerShell, for some reason.
In all other terminals it just outputs ~2 (bash) or nothing at all (CMD)...
I have tried:

  • Cygwin (bash)
  • CMD
  • Debian in WSL (bash)

I'm running Windows Terminal (Preview)
Version: 0.6.2951.0
Windows 10 Enterprise, Version 10.0.18362 Build 18362

This is from my keybindings config (oh, and ctrl+shift+v works so the config seems to be correct):

    "keybindings": [
        {
            "command" : "paste",
            "keys" :
            [
                "shift+insert",
                "ctrl+shift+v"
            ]
        },
        {
            "command" : "copy",
            "keys" :
            [
                "ctrl+insert",
                "ctrl+shift+c"
            ]
        }
    ]
@tovine commented on GitHub (Nov 22, 2019): This still doesn't work for me... Except for in PowerShell, for some reason. In all other terminals it just outputs `~2` (bash) or nothing at all (CMD)... I have tried: - Cygwin (bash) - CMD - Debian in WSL (bash) I'm running Windows Terminal (Preview) Version: 0.6.2951.0 Windows 10 Enterprise, Version 10.0.18362 Build 18362 This is from my keybindings config (oh, and `ctrl+shift+v` works so the config seems to be correct): ``` "keybindings": [ { "command" : "paste", "keys" : [ "shift+insert", "ctrl+shift+v" ] }, { "command" : "copy", "keys" : [ "ctrl+insert", "ctrl+shift+c" ] } ] ```
claunia commented 2026-01-30 22:56:56 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 22, 2019):

Sorry -- this is a doc fail for us. keys is for chording (where you must press all the keys in the list, in order). You'll want to just add another {"command":... "keys"...} instance to bind the inserts

@DHowett-MSFT commented on GitHub (Nov 22, 2019): Sorry -- this is a doc fail for us. `keys` is for _chording_ (where you must press all the keys in the list, in order). You'll want to just add another `{"command":... "keys"...}` instance to bind the `inserts`
claunia commented 2026-01-30 22:56:56 +00:00
Author
Owner
Copy Link

@tovine commented on GitHub (Dec 3, 2019):

You're right, thanks a lot for the tip! 😄

@tovine commented on GitHub (Dec 3, 2019): You're right, thanks a lot for the tip! 😄
claunia commented 2026-01-30 22:56:56 +00:00
Author
Owner
Copy Link

@evolite commented on GitHub (Dec 17, 2019):

Sorry -- this is a doc fail for us. keys is for chording (where you must press all the keys in the list, in order). You'll want to just add another {"command":... "keys"...} instance to bind the inserts

Sorry, Could you please specify how the configuration should look in order to make shift-insert paste work? Not quite getting it to work here.

edit: nvm, i read your post again

for others:

    "keybindings": [
    {
        "command" : "paste",
        "keys" :
        [
            "shift+insert"
        ]
    },
    {
        "command" : "copy",
        "keys" :
        [
            "ctrl+insert"
        ]
    }
]
@evolite commented on GitHub (Dec 17, 2019): > Sorry -- this is a doc fail for us. `keys` is for _chording_ (where you must press all the keys in the list, in order). You'll want to just add another `{"command":... "keys"...}` instance to bind the `inserts` Sorry, Could you please specify how the configuration should look in order to make shift-insert paste work? Not quite getting it to work here. edit: nvm, i read your post again for others: "keybindings": [ { "command" : "paste", "keys" : [ "shift+insert" ] }, { "command" : "copy", "keys" : [ "ctrl+insert" ] } ]
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#2502
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?