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

Add support for Windows clipboard history (Win+V) in bash #18580

New Issue
Closed
opened 2026-01-31 06:18:21 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 06:18:21 +00:00
Owner
Copy Link

Originally created by @happylynx on GitHub (Oct 2, 2022).

Add support for Windows clipboard history activated by Win+V in bash.

  • When running PowerShell, paste from clipboard history works ok.
  • When running bash in its own window (i.e. not using Window Terminal, from MSYS2 project or Git), paste from clipboard history works ok.
  • When running bash in Windows Terminal window (in any way - C:\Windows\System32\bash.exe, from Windows Subsystem for Linux, executable from Msys2, ssh connection to a Linux machine) and paste from clipboard history is activated, it does nothing for the first time and it prints ^V for the second time.

Version

Windows Terminal Preview, Version: 1.16.2642.0

Originally created by @happylynx on GitHub (Oct 2, 2022). Add support for Windows clipboard history activated by Win+V in bash. * When running PowerShell, paste from clipboard history works ok. * When running bash in its own window (i.e. not using Window Terminal, from MSYS2 project or Git), paste from clipboard history works ok. * When running bash in Windows Terminal window (in any way - `C:\Windows\System32\bash.exe`, from Windows Subsystem for Linux, executable from Msys2, ssh connection to a Linux machine) and paste from clipboard history is activated, it does nothing for the first time and it prints `^V` for the second time. #### Version Windows Terminal Preview, Version: 1.16.2642.0
claunia added the Needs-TriageNeeds-Tag-FixNeeds-Author-Feedback labels 2026-01-31 06:18:22 +00:00
claunia commented 2026-01-31 06:18:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 3, 2022):

Do you have ctrl+v bound to paste in your settings/? Clipboard History works by just sending a literal ctrl+v key to the window, so if that's not bound to paste, then it won't work for pasting.

@zadjii-msft commented on GitHub (Oct 3, 2022): Do you have `ctrl+v` bound to paste in your settings/? Clipboard History works by just sending a literal ctrl+v key to the window, so if that's not bound to paste, then it won't work for pasting.
claunia commented 2026-01-31 06:18:23 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 7, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Oct 7, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
claunia commented 2026-01-31 06:18:23 +00:00
Author
Owner
Copy Link

@SaltyChiang commented on GitHub (Oct 26, 2022):

@zadjii-msft It is annoying to bind ctrl+v to paste while using vim. Vim default bind ctrl+v to toggle visual block mode which is very useful. Is there any workaround to make clipboard history work without editing the default key binding in vim? As mentioned above, clipboard history works well in mintty shipped with msys2.

@SaltyChiang commented on GitHub (Oct 26, 2022): @zadjii-msft It is annoying to bind `ctrl+v` to paste while using vim. Vim default bind `ctrl+v` to toggle visual block mode which is very useful. Is there any workaround to make clipboard history work without editing the default key binding in vim? As mentioned above, clipboard history works well in mintty shipped with msys2.
claunia commented 2026-01-31 06:18:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 26, 2022):

This is just a quick thought, but you might be able to bind ctrl+v to multipleActions([paste, sendInput('^V')]), so that when Terminal receives a Ctrl+V, it both pastes, and sends a literal ^V to the client application (that vim can read).

I have not tested this, but it's a thought.

@zadjii-msft commented on GitHub (Oct 26, 2022): This is just a quick thought, but you might be able to bind ctrl+v to `multipleActions([paste, sendInput('^V')])`, so that when Terminal receives a Ctrl+V, it both pastes, and sends a literal ^V to the client application (that vim can read). I have not tested this, but it's a thought.
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 Needs-Author-Feedback Needs-Tag-Fix Needs-Triage
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#18580
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?