Skip to content

Can't map Windows+V as the shortcut key #216

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

Open
MangelMaxime opened this issue Feb 11, 2025 · 3 comments
Open

Can't map Windows+V as the shortcut key #216

MangelMaxime opened this issue Feb 11, 2025 · 3 comments

Comments

@MangelMaxime
Copy link

Hello,

When trying to set Win+V for the shortcut key windows always display its own Clipboard manager suggestion.

To workaround this limitation I used AutoHotKey to capture Win+V and send the shortcut I configured in PasteBar.

I also found that PasteBar don't seems to allows settings any shortcut that use Win+<any key>

@kurdin
Copy link
Contributor

kurdin commented Feb 11, 2025

@MangelMaxime Windows does not allow assigning custom application shortcuts to Win + any letter key combinations because most Win key shortcuts are reserved by the system (e.g., Win + V opens the Clipboard History).

@MangelMaxime
Copy link
Author

@kurdin Oh I didn't know that.

Because AutoHotKey can do it, I assumed it was a bug in PasteBar but perhaps this is limitation like you mention.

@kurdin
Copy link
Contributor

kurdin commented Feb 11, 2025

@MangelMaxime Yeah, AutoHotKey might be doing something else but I'll double check if this is possible with library I use for system shortcuts management.

Here is what I found from AutoHotKey documentation.

Hotkeys that include Win (e.g. #a) will wait for Win to be released before sending any text containing an L keystroke. This prevents usages of Send within such a hotkey from locking the PC.

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants