mklcp

Well, I don't know what to do then. The problem is still present when I trim down my bashc to: ```` export PATH="$PATH:$HOME/.local/bin/fzf/bin" export FZF_HOME="$BIN/fzf" [[ $- == *i* ]]...

Hey there, just to say that I'm using non-english vosk models, along with non-qwerty keyboards that are heavily customized (think caps lock and num lock always active, 8 levels of...

Ydotool also had issues with my setup

it seems that `foo(){ return 0 }` is incorrect by design ( https://stackoverflow.com/questions/38595559/how-to-define-a-function-on-one-line ) and when I try to execute it with bash 5.1.4(1), it fails

@Johni0702 Any updates? This is a killer-feature for me and your proposal looks really promising.

This is possible with `multi` I think, at least in KMonad it's possible

Just bethinking how to improve this improvement: As I understand it, this PR is based on the 3rd option of https://github.com/kmonad/kmonad/issues/157#issuecomment-774503161 This solution gives more granularity because each touch that...

> I don't think that this proposal composes well when used with multi-function keys, e.g. combining with tap-hold. Here the chording is implicit, and one can't choose to do chording...

I found another use of this proposal: it solves https://github.com/kmonad/kmonad/issues/487 The issue is that some non-programmable keyboards have fancy keys that don't have a dedicated keycode. The example described in...

> For my preference, I like the existing functionality more, with the reasoning that it feels cleaner from a design perspective. In the existing functionality, the chord action acts only...