-
Notifications
You must be signed in to change notification settings - Fork 187
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
Uppercase letter not considered symbol and resets the overloadi timer #875
Comments
What if you use a macro? I dont recall correctly and will probably check when i get home and have time to check the config, but there probably is a macro repeat action or something similar. Check the manpage |
What if you used If you change all keys to be like that you will have auto capslock if you tap any key less than 100ms. |
This is not exactly the same. What I want is to trigger the uppercase version if the last non-action key (that was typed before the current key) was less than 100ms ago. |
Sorry for the delay.
This is indeed a bug and should be fixed in the latest commit. I am closing this tentatively, but feel free to reopen it if the bug isn't fixed. |
* man: Add note about config file exclusivity * readme: Add explicit mention of wayland (rvaiya#559) * man: Add note about maximum layer name length * config: Allow 64 character layer names (rvaiya#558) * Long overdue release * docs: Fix changelog typos * readme: Update arch package location This has been imported into Arch's [extra] repository. * make: Move service generation into install target (rvaiya#801) * config: Increase the nested descriptor limit * Enable GNOME extension for v47 * overloadi: Account for shifted symbols (rvaiya#875) * Update README.md since it says "Install AND start" adding `--now` might make more sense! * keyd-application-mapper: Add support for the pop-os cosmic desktop * keyd-application-mapper: Fix wlroots support for new windows * readme: Combine systemctl `enable` and `start` commands by using `--now` * readme: Fix broken QMK link * ipc: Explicitly account for failure in the early stages of the connection (eliminates annoying compiler warning) * evdev: Add support for AL_* family of keys found on some laptops * listen: Eagerly terminate on pipe closure to accommodate more scripting use cases * config: Make main a proper layout * doc: Add Half-QWERTY layout to examples This layout has been very useful to me for typing only with the right hand. I did not test it for left-handed typing. * doc: Add chromebook-linux.conf to examples * keyd-application-mapper: Fix string escape bug causing issues on some platforms (rvaiya#649) * layouts: Fix 0 in the FR layout * core: Add special case for volume key devices in capabilities check * doc: Add examples for common patterns. * doc: Add additional key mappings to the chromeos example * config: Increase macro size * core: Improve support for thinkpad keyboards (rvaiya#905) * layouts: Add graphite-angle-kp keyboard layout * layouts: Add graphite keyboard layout * core: Improve support for exotic mice * core: Fix compilation on older systems * Add support for scroll remapping * doc: Add macos example to the readme * Tweak readme example * Improve mouse button support * Add missing entries ` for the letter ḏal Shift + ` for the shaddah Shift + 0 for left parenthesis * Add eastern Arabic zero * core: Avoid interpreting remapped keys as part of a panic sequence (rvaiya#929) * layout: Update graphite-angle-kp Corrected a key, it was just a typo I guess. ref : https://github.com/rdavison/graphite-layout * doc: Update the application mapper man page Clarifies that the verbose flag is needed to see window events in the output. * keyd-application-mapper: Process SIGUSR1 on wayland (rvaiya#935) * macro2: Fix timeout bug for nested macros * doc: Update README * keyd-application-mapper: Refactor wayland code Clean up Wayland() and allow binding to multiple protocol objects simultaneously * timeout: Add new behaviour when used as a tap target (rvaiya#879, rvaiya#738, rvaiya#944) This patch expands the semantics of timeout() to cover the case in which it is used as a tap target. This facilitates a number of novel use cases, like discriminating between single/double tap or implementing per-key oneshot timeouts. Specifically timeout() is now defined in terms of arbitrary key events rather than the behaviour of the key to which it is bound (if any). The new definition executes the second action if no key events occur before the timeout expires. The implication of this is that when timeout() is executed as the result of a tap action, action2 will be executed after the timeout expires unless another key is struck in the interval. Note that this is backward compatible with the old definition, since a key up event (i.e a tap) will result in a resolution to the first action if timeout() is directly bound to a key. For Example: tab = overload(control, timeout(a, 100, b)) will presently produce no effect when 'tab' is tapped. Under the expanded definition, tapping tab will produce 'b' if 100 milliseconds elapse without an interceding key event. * macro: Eagerly restore modifiers post execution (fixes rvaiya#947) * macro: Ensure modifier state is properly tracked during macro execution --------- Co-authored-by: Raheman Vaiya <[email protected]> Co-authored-by: ainola <[email protected]> Co-authored-by: birdbird <[email protected]> Co-authored-by: Chris Schepman <[email protected]> Co-authored-by: Pavel Slepushkin <[email protected]> Co-authored-by: blankie <[email protected]> Co-authored-by: Rajas Paranjpe <[email protected]> Co-authored-by: diegorodriguezv <[email protected]> Co-authored-by: Egor Pasko <[email protected]> Co-authored-by: Merith <[email protected]> Co-authored-by: Ridwan Mulyadi <[email protected]> Co-authored-by: Fleefie <> Co-authored-by: Garbaz <[email protected]> Co-authored-by: Leandro M. Peralta <[email protected]> Co-authored-by: Dick Marinus <[email protected]> Co-authored-by: aljustiet <[email protected]> Co-authored-by: Justin <[email protected]> Co-authored-by: Awelaa <[email protected]> Co-authored-by: Cédric <[email protected]> Co-authored-by: Robert Benson <[email protected]>
Here is my config.
I was expecting to be able to keep entering uppercase
Q
when repeatedly pressingq
because it would trigger<action 1>
as I keep below 1000ms. However, it seemsS-q
is not considered a "non-action" (or symbol). So every 1000ms, I have<action 2>
triggered.Is there a way to make it consider that
Q
is a "regular symbol key"?I tried this, but same result:
And for context, I am trying to active a mode/layer where everything I type is uppercase as long as I keep typing below 1s. It would be kind of a smart capslock that would deactivate itself is no key is entered for 1s.
The text was updated successfully, but these errors were encountered: