Skip to content

[Bug] one-shot shift never releases shift with certain custom shifts #65

@rosshadden

Description

@rosshadden

Describe the bug

If I use a one-shot shift like OSM(MOD_LSFT) on a key with a custom shifted value, it does indeed type the custom shifted value as you would expect. However for some custom shifts it seems like the shift key becomes "stuck" after that point, and all keys get typed shifted until you "unstuck" shift. I do this by just long pressing and releasing the same shift key (making it bypass the one-shot functionality).

Most custom shifted keys work totally fine with one-shot shift. The three I have found so far to have this problem are \, =, and ;. I use a modified Engram layout, with these key:shift pairs: 1:\ 2:= ,:;. All other custom shifted pairs seem to work great (which is why it took me a while to even realize this was happening).

I do use achordion but this problem occurs regardless of which one-shot shift used.

Information

Do the keys involved use any of the following features?

  • Achordion (from this repo)
  • Auto Shift
  • Combos
  • Key Overrides
  • Mod-tap or Layer-tap keys
  • Other custom userspace code:

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions