Skip to content
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

Certain keyboards lack LCtrl key - makes config access difficult #158

Open
crushallhumans opened this issue Sep 23, 2024 · 4 comments
Open

Comments

@crushallhumans
Copy link

crushallhumans commented Sep 23, 2024

Hi - I use an Advantage2 Kinesis ergonomic keyboard in a MacOS config, and it lacks a LCtrl key. My control key set is LCmd, LOpt, RCtrl, RCmd. When I need to reprogram the deskhop, I have to haul out a standard keyboard and swap it in, in order to trigger the LCtrl + RShift + C + O setting. Not a huge deal, but I figured I'd make you aware.

@hrvach
Copy link
Owner

hrvach commented Sep 23, 2024

I definitely suck at choosing hotkeys. What's a reasonable key combo that all keyboards would have, but you would never trigger accidentally? Every single one I choose has a clash with some keyboard model :)

@crushallhumans
Copy link
Author

That does seem like a game of whack-a-mole. How long can the chord sequence be? Like can it be 'hold(either Ctrl + either shift) and then press in sequence (L, U, K, N, M)'? I've seen this multi-step command sequence used in IDEs, where huge numbers of hotkeys means a need for the second register of command keystrokes.

@hrvach
Copy link
Owner

hrvach commented Sep 23, 2024

The key sequence is doable but you'd have to store past keypresses internally, and I feel very uneasy storing e.g. somebody's freshly typed password in a buffer. Yes, it's only internally, but zero memory (aside from output queue) is on purpose and I'd hate to break it. I'll ask LLM for some suggestions, maybe it is able to suggest something my tiny brain can't think of :)

@crushallhumans
Copy link
Author

That makes sense to me, and the rigor of never storing data at all is a good one and worth defending. Maybe it makes sense to just duplicate the invokation set, so (Lshift + Rctrl) || (Rshift + Lctrl) + C + O works - that solves for my issue, and I think it's a fair guess that all keebs will have an one set of opposed shift and ctrl. Unless they're fully programmable - which mine notionally is but I can't get into the utility to inject a new keycode into it :) Thanks for the strong engagement - I love the product and hope it's successful!

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