[GH-ISSUE #331] Apply modifiers toggle doesn't work when using CTRL+SHIFT #283

Open
opened 2026-05-05 05:11:40 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @antoaenono on GitHub (Sep 24, 2025).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/331

with the Apply Modifiers setting checked
SHFT + , correctly produces <

but
CTRL + SHFT + , does not convert the SHFT + , to <
in other words, CTRL + SHFT + produces CTRL + SHFT +

maybe this is the intended behavior
but I would expect
CTRL + < to be displayed instead of CTRL + SHFT + ,

Originally created by @antoaenono on GitHub (Sep 24, 2025). Original GitHub issue: https://github.com/keycastr/keycastr/issues/331 with the _Apply Modifiers_ setting **checked** SHFT + , correctly produces < but CTRL + SHFT + , does not convert the SHFT + , to < in other words, CTRL + SHFT + produces CTRL + SHFT + maybe this is the intended behavior but I would expect CTRL + < to be displayed instead of CTRL + SHFT + ,
Author
Owner

@akitchen commented on GitHub (Sep 24, 2025):

Yes, you are correct, there is a subtle bug here coming from the older intentional choice to always show the original keycap for command sequences.

Another annoying example is in the US-English layout: + is a shifted =, and in many apps there is a common keystroke to zoom in which is CMD-+ but KeyCastr will display CMD-Shift-= instead.

Maybe this can be handled better now that we have the setting to apply modifiers, but keep in mind that there would likely be other undesirable results, especially in the number row. I'll look into it...

Thanks for the bug report!

<!-- gh-comment-id:3330978384 --> @akitchen commented on GitHub (Sep 24, 2025): Yes, you are correct, there is a subtle bug here coming from the older intentional choice to always show the original keycap for command sequences. Another annoying example is in the US-English layout: + is a shifted =, and in many apps there is a common keystroke to zoom in which is CMD-+ but KeyCastr will display CMD-Shift-= instead. Maybe this can be handled better now that we have the setting to apply modifiers, but keep in mind that there would likely be other undesirable results, especially in the number row. I'll look into it... Thanks for the bug report!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/keycastr#283
No description provided.