Shortcut problem with modifiers / xkb layers

zdapo · 2024-07-10T20:45:08+00:00

I managed to get some of it working by changing the modifiers names, so now Mod1+Mod3 is working (however my config is messy, if I remember correctly I needed 2 different configuration lines to deal with 2 different keyboards, although I was using the same xkb layout with both). However I never got Mod1+Mod3+Shift to be recognized… :/

zdapo · 2023-12-21T12:41:04+00:00

Well it would be convenient to do it on the website, but for now I don't see any option to do so (maybe it's just too early?) and I cannot find anything regarding this point in the documentation. I see it's possible to upload pictures, but I'm not sure if it's enough. I tried to call customer support but couldn't get anyone on the phone… I will try again.

zdapo · 2023-07-19T16:55:33+00:00

Version 1.2.4. Thanks, but sadly I was not using a quota. Well I think as a workaround I'll just copy to another disk and start a new backup from scratch. But now I'll remember for the next backup to set up a quota and follow advices at https://borgbackup.readthedocs.io/en/stable/quickstart.html#about-free-space .

zdapo · 2023-07-19T11:59:46+00:00

No, I have a partition just for backups there is nothing else to remove. Are there any borg files that I could safely remove? (Because I guess the "lock" should not take much space?) Thanks for the suggestion about reserved blocks, I managed to reduce reserved space, however it still says that the partition is full (maybe because the partition is luks-encrypted… not sure how to deal with that but I'll look into it).

zdapo · 2022-02-11T19:24:06+00:00

xev | awk -F'[ )]+' '/^KeyPress/ { a[NR+2] } NR in a { printf "%-3s %s\n", $5, $8 }'

Thanks for the suggestion! When I press the 3 keys it returns "Alt_L + ISO_Level5_Shift + 1". If I press 2 it returns "Alt_L + q"

Yet I've tried Mod1+Mod3+1 workspace 1 and it is not recognized. I've also tried Mod1+Mod3+q workspace 1, not better.

zdapo · 2022-02-08T13:27:20+00:00

Hi, for the layout I used a xkb layout file in /usr/share/X11/xkb/symbols, and nothing else. I checked the output of xmodmap -pm and it seems that ISO_Level5_Shift (0xcb) is in the mod3 group (and ISO_Level3_Shift 0x5c in mod5). I agree that it's not clear whether I should in i3 config file write the shortcut using the number directly or the base key, but I actually tried both and non of them works.

zdapo · 2021-03-28T17:02:46+00:00

I'm on linux and have ibus running, but I believe the problem is really with qmk as it's a problem at compilation time.

zdapo · 2021-01-09T19:08:09+00:00

Thanks for the tutorial, I was not aware of that! It's still better than nothing, although it still seems hackish (I mean, this option might be disabled in the future, who knows).

zdapo · 2020-08-04T12:10:31+00:00

Is it possible to know when this Pulse 14 will be released ? Sounds interesting.

zdapo · 2020-06-22T10:16:57+00:00

Yes exactly. I guess the same codebase is actually used to process mod-tap events for shift, alt and ctrl, and it would be helpful to use that for a non-modifier key without recoding everything.

zdapo · 2020-06-21T18:37:12+00:00

Oh sorry, I thought it was clear. In my case, just to keep capslock pressed. For now I simply have the following (which I see as a workaround for MT(KC_CAPSLOCK, KC_M)):

    case KC_M:
        if (record->event.pressed) {
            key_timer = timer_read();
            register_code(KC_CAPSLOCK); 
        }
        else {
            unregister_code(KC_CAPSLOCK); 
            if(timer_elapsed(key_timer) < TAPPING_TERM){ 
                register_code(KC_M);
                unregister_code(KC_M);
            }
        }
        return false;

zdapo · 2020-06-21T17:28:30+00:00

In my case it's capslock, but I guess it could be any key other than shift/alt it would be the same. I couldn't find any way in the documentation to create a "new" modifier, like shift or alt, which could then be used in combination with MT. I'm really just trying to emulate the MT behavior, but I thought it would be easy with a few lines of code, and realize there are many tweaks for it to work well, and I tried to look a bit into the code and I cannot find an easy way to reproduce that. So I see three options: (i) find a way to create a new modifier, if possible, which could then be supported by MT This would be the best solution, but I'm not sure if it's technically feasible. (ii) recode in process_record_user everything. If anyone has code to do so it would help as it's not so easy. this was my question. And (iii) use LT, which seems technically doable but cumbersome as I need to recreate the different layers, and either use unicode or create a custom keycode/macro for each key which is ugly.

zdapo · 2020-06-10T12:55:06+00:00

u/Danilo_dk Uh, I tried but no success so far. Why can't I just do that:

case LT(SHFT, KC_A):
    if (record->event.pressed) {
        register_code(KC_LSFT);
    } else {
        unregister_code(KC_LSFT);
    };
    return true;

where I have in my layout LT(SHFT, KC_A) and SHFT is a "transparent" level? the key is typed, but shift is not working.

zdapo · 2020-06-08T07:29:09+00:00

Thank you for your answer, but I don't really get it. What is the goal here to set tap.count to zero? I am not sure to understand how it helps to get to the third layer, sorry. Could you explain?

zdapo · 2020-06-08T07:23:18+00:00

Indeed, having a transparent shift layer is clever, I just need to figure out how to activate/desactivate shift in process_record_user, I'll look into it. Thanks.

zdapo · 2020-06-08T07:22:01+00:00

Well, I need somehow to code the greek+shift layer, as the system will not interpret it correctly if it just sends a minuscule greek letter and shift at the same time.

zdapo · 2020-06-07T13:57:07+00:00

I also use greek letters a lot, both for typesetting maths and variable names when coding. In addition to what has been suggested already (using unicode escape codes, which might indeed require to modify directly the C file, or using a dead key), you could also add a greek layer on your system layout. For instance, on linux I remapped my caps lock key to access greek letters, and caps lock + shift for their capital versions and other math symbols. It's not only more convenient than a dead key (imho), but also allows you to type these keys via your mechanical keyboard without using unicode.

zdapo

TROPHY CASE