I'm using the extend layer option, after installing the xkb files on my system. All seems to work well on most applications, but the extend layer appears to break my "equal" symbol. The key doesn't produce any output on any of my applications. Strangely, the second level of the key, "+" works fine.
Looking at the output of xev I see that the key press event is not triggered, instead something else called KeymapNotify:

KeymapNotify event, serial 28, synthetic NO, window 0x0,
    keys:  4294967172 0   32  0   0   0   0   0   0   0   0   0   0   0   0   0   
           0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

KeyRelease event, serial 28, synthetic NO, window 0x5800001,
    root 0x784, subw 0x0, time 1107135, (490,431), root:(490,460),
    state 0x0, keycode 21 (keysym 0x3d, equal), same_screen YES,
    XLookupString gives 1 bytes: (3d) "="
    XFilterEvent returns: False

And here is the output of xev for the shifted version, that produces a + without problem:

KeyPress event, serial 25, synthetic NO, window 0x5800001,
    root 0x784, subw 0x0, time 5845125, (399,579), root:(399,608),
    state 0x0, keycode 50 (keysym 0xffe1, Shift_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyPress event, serial 28, synthetic NO, window 0x5800001,
    root 0x784, subw 0x0, time 5845311, (399,579), root:(399,608),
    state 0x1, keycode 21 (keysym 0x2b, plus), same_screen YES,
    XLookupString gives 1 bytes: (2b) "+"
    XmbLookupString gives 1 bytes: (2b) "+"
    XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0x5800001,
    root 0x784, subw 0x0, time 5845389, (399,579), root:(399,608),
    state 0x1, keycode 21 (keysym 0x2b, plus), same_screen YES,
    XLookupString gives 1 bytes: (2b) "+"
    XFilterEvent returns: False

KeyRelease event, serial 28, synthetic NO, window 0x5800001,
    root 0x784, subw 0x0, time 5845735, (399,579), root:(399,608),
    state 0x1, keycode 50 (keysym 0xffe5, Caps_Lock), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False

Hello there!

I noticed that the US variant of the Colemak layout have a DH version, but currently there is no DH variant for Portuguese (Brazil) for both keep local symbols and unified symbols.

This can be circumvented by ticking the Colemak Curl (DH) ergo Mod option inside Miscellaneous compatibility options in the Advanced tab on the keyboard setting on KDE Plasma (Screenshot below), but I game a lot and Wine/Proton does not support dynamically changing your keyboard layout, so it defaults to the first one in the system settings. Having a DH layout in Portugese for both variants I listed above would fix this since there would be no need to keep Colemak as the first layout on the list.

Hi,

I'm still loving all of @DreymaR 's KbdTrix and they've been indispensable to me, both on Linux with xkb and on Windows with PKL.

I've just installed Synergy by Symless in order to share my Microsoft Sculpt keyboard across my Linux workstation and my Windows Laptop.

The way I have it set up is with Windows as the host and Linux as the client. The problem is that keys are not coming across correctly to the Linux client. Some comments that I found on the web said that running setxkbmap after starting the synergy client with synergyc might help but it didn't in my case.

Do you have any experience with this or seen anything in the Colemak forums?

Hello Dreymar. I am trying to integrate your work in NixOS, so I could modify the xkeyboard-config package.

Due to the way Nix stores files, after downloading your repo, it is stored under /nix/store/hash-source, a different path than the upstream xkeyboard-config clone. This separation makes it impossible for your scripts to search in /usr/share/X11, because they're simply not stored there. Also, it wouldn't be possible to hardcode the path, as the hash changes based on what's inside the package.

It is, however, possible to reference the location of xkeyboard-config while building Nix packages. Because of that, I'd like to be able to specify that location as an option for your script, similar to the -i option.

Is it possible to integrate such an option? I could fork and make the changes on my end, then open a PR.

Perhaps a stupid question, but I am stumped.

There is a reference in the help text to a -# option, but each time I run ./setxkb.sh -# I get an error saying that is not an option 🤔

using the restore option of the install script, files installed by it previously are still there after the operation. I also don't seem to be able to remove them neither by reinstalling the package that own the keyboard config in my system. I mean, I like those changes up to now, but I was trying a complete reinstall of xkb and the trick bag as part of a debug investigation. I have to say though, that those scripts looks like a lot of work, in the good sense.

How can I convert a folder of layouts that I created for EPKL on Windows to use on Linux with XKB?

Hi Øystein

I’ve used your angle-wide layout for years and I am totally addicted to it!. Colemak is so great and your modifications make it even greater.

It’s great that you added the TTYs on Ext+AltGr; I don’t think Ctrl+Alt+Fx ever worked for me for some reason.

I’ve been using the version from around 2014 I think, where the Ext+Q combination works as Escape. As a frequent Vim user this has been very useful to me. But I couldn’t get this to work in newer versions. I was excited to see in the commit log that you tried to fix this issue lately, but it is still not working for me. If there’s anything I can do to help troubleshoot this issue, please let me know.

Just so you know, I’m loading the keyboard layout in a particular way, like this (I’ve copied the xkb directory to /usr/local/share/X11, but I don’t think the way you load it should have any effect on the outcome):

cd /usr/local/share/X11/xkb
setxkbmap \
  -rules evdev \
  -model pc105aw-sl \
  -layout no \
  -variant cmk_ed_us \
  -option '' \
  -option misc:extend \
  -option lv5:caps_switch_lock \
  -print \
  | xkbcomp -I -I/usr/local/share/X11/xkb -I/usr/share/X11/xkb - $DISPLAY

Thanks again for your great work!

Hey,

I recently came across klfc which looks very cool. You can describe your keymappings in json in an OS independent way, and it can generate configs for XKB, PKL, KLC, keylayout, TMK and AHK.

Thought you may be interested in using this, especially given how painful it is to work with xkb :)

When I set the misc:extend option in setxkbmap Ctrl+Alt+F1 doesn't take me to a virtual console anymore. Do you know what could cause that?

Thanks!

I applied the the Mod-DH rules to my Dell XPS using the install-dreymar-xmod.sh script from the repository and I noticed that all was applied right except the D and the V keys were in the wrong location. I still suck at finding the config XKB files so I can't tell if it is a typo in the file, or an error in applying to my laptop, which is running Fedora 27 GNOME

I have tried doing the SYM mod manually, however it does not work. I changed order and few keys needed, and recursively included of the 105aw-sl model and the 104aw-zqu, however it does not have any effect. The changing was only done in geometry/pc not the symbols/colemak file, so for example the order of my last characters in the top row is , , , { , ...

I do not use the script, but I did both a manual copy to /usr/share/X11... and the linking method used in one of the tickets xkbcomp -I...

Sorry I am on mobile with no other choice atm, so I cannot copy paste the exact code and command blocks.

Oh and awesome work for the past fifteen years Dreymar, thank you for your input!

According to:
= should come before the 6, however when using xkb the 6 comes first. To fix this in /keycodes/evdev, replace

xkb_keycodes "pc105wide-rightpart" {

    <AE12> =  16;	// =	<  7

with

xkb_keycodes "pc105wide-rightpart" {

   <AE12> =  15;	// =	<  6
   <AE06> =  16;        // 6    <  7	

Hi,

Your extend layer is amazing! Thank you!

I made a few modifications for my own. I actually tried a lot of variations and for a lot of them I came back to your original mappings. Some of them I am keeping for now. Happy to share or pull request if you're interested.

Anyway, they all work great on my Windows laptop with PKL. However on my Linux box a lot of the multi-key mappings don't work. In particular Alt+Tab and most of the Alt+? , Shift+? and Ctrl+? mappings.

Do you have any experience or suggestions for going about trying to resolve these problems? I have a Microsoft Ergonomic keyboard in case that makes any difference. I don't know if that doesn't handle simultaneous scancodes properly or something like that. Any comments would be appreciated.

Thanks again for making this available!

Hi! Thanks for the very wonderful implementation of these layout switcher!

I have both a window and linux machine. I found that your OSD (on screen display) in windows is extremely useful, especially for getting used to the powerful extended layer ∩(◕‿◕｡)∩～♪

Would it be possible to have something like that in linux as well? (is it already possible?) It would be extremely handy to have it around. Thanks!

Host OS: Arch Linux
VirtualBox Version: 6.1.30 r148432
Steps to reproduce:
Install Xubuntu 21.10 in a VirtualBox VM
Install git, then clone https://github.com/DreymaR/BigBagKbdTrixXKB.git
Install big bag using bash install-dreymar-xmod.sh -o "4caw us us"
Reboot VM
Set keyboard layout with bash setxkb.sh -a "4caw us us"
Try shortcuts involving Super+[Tab, D, E, F, L, etc]

Recorded a video in my VM for demonstration, with python3-pip and python3-xlib additionally installed so I could install key-mon to show keypresses. When I used Xubuntu 21.10 on bare metal with big bag installed like this, Super+L behaved like it did in this vid, but I didn't test the other shortcuts.

When messing around with setxkbmap, I noticed a lack of a Left alt as extend option. It'd be nice to have it though.

Good day sir.

I got everything setup by running the install script, and I could access Colemak in my appropriate language 👍 The only thing I was missing was the Angle mod (shifting the keys on zxcvb to the left, to use the iso specific key to the right of left-shift).

I found in the issues here that one has to "Set the keyboard model appropriately" which is then clarified later on here that this means an OS specific setting on ones system, and not a configuration in this repo / the setup (surely easily confused with the "model" -m option in the scripts). Long story short: I cannot seem to do this on my system (Pop OS 22.04 on a Dell Inc. XPS 13 9380) and I did look quite a bit. You comment on this difficulty in these later distros later in the thread 👍 Not only can I not find such an option anywhere, nor by searching, but even if I did find it I have no clue what I'd end up putting there! All this pc105 hardware code nonsense will be the death of me! 💀

Manually fixing it

The below is surely only suitable on my personal system for the exact setup that I want on my particular hardware!

Soo I manually changed the XKB file that gets installed to add the Angle mod 👍 (Located at /usr/share/X11/xkb/symbols/colemak for me).

This at line 160 (before the curly close)

       include "colemak(cmk_ed_dh_manual_angle_fix)"

This just below that (after the curly close)

        hidden partial alphanumeric_keys
        xkb_symbols "cmk_ed_dh_manual_angle_fix" {
            include "colemak(manual_angle_on_iso)"
            include "colemak(cmk_ed_hm)"
        };

        hidden partial alphanumeric_keys
        xkb_symbols "manual_angle_on_iso" {
            key <AD05> { [             b,             B,  enfilledcircbullet,          Greek_beta ] }; // QWE T Cmk G
            key <AC05> { [             g,             G,                 eng,                 ENG ] }; // QWE G Cmk D
            

            key <LSGT> { [             z,             Z,               U0292,               U01B7 ] }; // QWE Z Cmk zZ ʒƷ
            key <AB01> { [             x,             X,              dagger,        doubledagger ] }; // QWE X Cmk xX †‡
            key <AB02> { [             c,             C,           copyright,                cent ] }; // QWE C Cmk cC ©¢
            key <AB03> { [             d,             D,                 eth,                 ETH ] }; // QWE G Cmk dD ðÐ
            key <AB04> { [             v,             V,            division,         Greek_gamma ] }; // QWE V Cmk vV ÷γ
            key <AB05>	{ [            less,          greater,      backslash,            notsign ]	};
        };

What's the point of this issue?

I just have two points

1. Oh grand wizard of keyboard codes and layouts: can you foresee an issue for myself by doing this? 🤔 I am on Christmas break now, so I haven't tried it on an external keyboard, but I presume it'd work 😅

2. If there is no issue: then I leave this here for the archives so someone may follow in my steps, towards the goal of grand masters of the martial art known as Colemak 🖖

Hello, first of all I want to thank you for your fantastic work on the extend layer. I had something similar programmed in the keybindings of my main applications since many years and was trying to implement something similar with xkb to have it system-wide. I've spend countless hours fighting with xkb without success; finding your work was such a relief. That's splendid in term of ergonomic. I couldn't find another way to contact you so I'm thanking you here.

Now for the problem at hand. The extend layer is working correctly in the few application I've tried up to the moment I opened VS-Code. Note that I am using the extend on top of my usual keyboard, for now a eurokey layout that is a classic us layout with an improved 3rd level.

First, with the word movements. To move a word left or right I first maintain pressed capslock(level5) + F(ctrl). VScode first opens the search widget, because it somehow detected a ctrl+f press. So somehow the press contol of the extend layout went through, but at the same time also the f letter. A first workaround was for me to unbind the ctrl+f keybinding. Then to the next quirk.

Now trying to make a trail-select-word, usually given by shift+ctrl+arrow, I find again the same type of problem. Pressing capslock+f+d should give me the equivalent of ctrl+shift, but somehow the keybinding assigned to ctrl+shift+d get triggered. If I keep those three pressed, and then press J or L to move the cursor and select words, if works fine. But in the process that hybrid shift+ctrl+d was detected and a side window opened. Somehow again the software received the shift+ctrl from the keyboard map, but at the same time detected on it's own that the letter key have been pressed.

As debugging information, using xev in a terminal shows me no trace of receiving the D letter when pressing and maintaining, in order, capslock and D.

I imagine it's maybe not directly related to your layout, but indirectly. The question is, is it possible for applications to read directly the key presses and do their own interpretation of them, and at the same time accessing the output of xkb? How is it possible that this application get the ctrl from your layout when I press capslock+f, and at the same time detect a f, which is like the raw key press? And conclude to trigger the ctrl-f keybinding? Or could it be that the capslock key would be considered as release, thus also sending the f key afterward? But in this case after removing the keybinding, and pressing capslock+f, I don't see any f printing?

All of this is pretty mysterious. Any idea what kind of mechanism is at work here?

Hello,

At first reboot after installing, gdm refused to start, and let me to deal with finding the issue from terminal.
I finally got to this:

Which lead me to this broken line:

After fixing it, gdm accepted to start normally.

This was on a Ubuntu 20.04.
When I then installed on a 22.04, the behaviour was different. Gdm started fine, and I could log on. But keyboard was in qwerty for most windows, except, oddly for firefox and gimp, who were using the intended layout (4caws). I also noticed the layout selector in top right corner of gnome was missing.

After fixing the evdev.xml file in the same way, and rebooted, things went a bit better, but not fully. Ie. it's like most windows and gnome seems to use something like 4ca (which I have never configured or tried on this machine), but firefox and gimp do use the expected 4caws.

Maybe that one could be related to wayland. But I don't even know which compositor is used by default...

Extended has change my typing life and now I'm no longer angry at laptop keyboards -- thanks. I am trying to setup the Extended Extreme mapping on a Linux Mint 18.04 system (based on Ubuntu 18.04) but it crashes with the following error in ~/.xsession-errors

Internal error:   Could not resolve keysym XF86ScrollRight
Error:            Button must specify default or be in the range 1..5
                  Illegal button value 6 ignored
Error:            Illegal action definition for <AD02>
                  Action for group 1/level 6 ignored
Error:            Button must specify default or be in the range 1..5
                  Illegal button value 7 ignored
Error:            Illegal action definition for <AC02>
                  Action for group 1/level 6 ignored
Internal error:   Could not resolve keysym XF86ScrollRight
Error:            Button must specify default or be in the range 1..5
                  Illegal button value 6 ignored
Error:            Illegal action definition for <AD02>
                  Action for group 1/level 6 ignored
Error:            Button must specify default or be in the range 1..5
                  Illegal button value 7 ignored
Error:            Illegal action definition for <AC02>
                  Action for group 1/level 6 ignored

To reproduce I installed the config from doing:

git clone https://github.com/DreymaR/BigBagKbdTrixXKB.git 
cd !$
sudo ./install-dreymar-xmod.sh -o -x 4n us us

and I can select the Layout to Colemak in the Keyboard Preferences GUI. That works well but I want to go full blissful with Extended Extreme so I enabled the option (not knowing what to do):

Miscellaneous compatibility optoins >> Enable level5 Extend mappings (home position arrows etc)

But then my x-session immediately crashed. I took quite a while to figure out how to get X-Windows back, so here's how for the next person that runs into this:

gsettings set org.mate.peripherals-keyboard-xkb.kbd options '[]'

I'm not sure if I first have to enable other options in the keyboard preferences (like Level 5 modifier settings). Also, I don't know if I would use scroll right and left (my mouse scroll button in xev is attached to button 4 and 5 for up and down.

Please let me know if you know of a fix for this. Thanks.

Glen

Thank you so much for this wonderful configuration. I can't tell you how much it has made my life better!! XKB was really hard to understand and I was not having any luck until I found your code.

I see that in the extend config it says that copy,paste, etc was: "not working since Ub14.04?". I'm wondering if there is anything new in this regard.

My intended use is not actually copy/paste but to create mappings to help on the command line. For example, defaults are:
back a word - alt+b
forward a word - alt+f
delete word ahead - alt+d
delete to beginning - ctrl+u
delete to end - ctrl+k
etc....

As you can see, the functionality is scattered about on different sides of the keyboard and different modifiers. I was hoping to make dedicated keys on the extend layer for each of these functions but I assume it will not work just like the copy/paste.

Thanks a bunch!!!

I am having trouble getting extend to work with curl angle dh. I run
./setkb.sh 4ca
and get:

¤ ShortStr model/layout: pc104angle / us(cmk_ed_us)
¤ ShortStr lay. options: Curl(DH) - 'y'; Sym - 'n'.

¤ Changing dir to '/usr/share/X11/xkb'
¤ Looking for and removing any old .xkm server files
¤ Running setxkbmap command using the system XKB dir:

> setxkbmap -model pc104angle -layout us(cmk_ed_us) -option misc:extend,lv5:caps_switch_lock,grp:shifts_toggle,compose:menu,misc:cmk_curl_dh -v 9

Setting verbose level to 9
locale is C
Warning! Multiple definitions of keyboard model
         Using command line, ignoring X server
Warning! Multiple definitions of keyboard layout
         Using command line, ignoring X server
Trying to load rules file ./rules/evdev...
Success.
Applied rules from evdev:
rules:      evdev
model:      pc104angle
layout:     us(cmk_ed_us)
options:    misc:extend,lv5:caps_switch_lock,grp:shifts_toggle,compose:menu,misc:cmk_curl_dh
Trying to build keymap using the following components:
keycodes:   evdev(pc104angle)+aliases(qwerty)
types:      complete
compat:     complete
symbols:    pc+us(cmk_ed_us)+inet(evdev)+group(shifts_toggle)+compose(menu)+level5(caps_switch_lock)+extend(basic)+colemak(cmk_ed_dh)
geometry:   pc(pc104angle)

¤ Changing dir to '/home/user/git/BigBagKbdTrixXKB'

@@@ setkb.sh finished! @@@

which looks fine but extend backspace doesn't work in kde applications or konsole, but works fine in chrome. The arrow extend keys work everywhere though. I also tried to add the colemak layout via kde GUI keyboard settings but activating extend in the advanced tab completely disables ALL backspace features.

Having this be more compatible with KDE Keyboard gui would help greatly when swapping layouts and changing settings for casual users!

Sidenote but this k to m swap is milling ke haha! Need to retrain my muscle memory!

I want the u and o keys to toggle over whole words instead of going to the beginning or end of the line. I am using Linux Mint and the functionality of this is ctrl+arrow key. I'd also like to assign the original functionality of the u and o keys to n and "."

As the title says, setting setxkb,sh makes most F1 - F12 keys doesn't work (e.g. F5 to refresh), but any modifiers + (F1 - F12) key combos (e.g. Alt+F4) work fine everywhere.

I executed the script using setxkb,sh 4n us us, and using the command written automatically in the .bashrc:
setxkbmap -model 'pc104' -layout 'us(cmk_ed_us)' -option 'misc:extend,lv5:caps_switch_lock,grp:shifts_toggle,compose:menu

Both always make this problem appear in both of my machines.

My machines are currently running:

• Fedora 35 KDE 5.23.3
• Fedora 33 KDE 5.20.5

Any suggestions on where to look for?

I'm using Fedora Gnome.

How to reproduce the issue:

1. run install-dreymar-xmod.sh
2. reboot
   -> no more Wayland menu entry in Gnome login screen: "Gnome with XOrg" becomes "Gnome". This last one was the choice for Wayland
3. restore original files in /usr/share/X11/xkb from automatic backup
4. reboot
   -> Wayland menu entry is back

I can still open a Wayland session through a TTY

Jul 16 17:09:52 remi-desktop systemd[1]: systemd 253.5-1.fc38 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +>
Jul 16 17:09:56 remi-desktop systemd[1]: systemd 253.5-1.fc38 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +>
Jul 16 17:09:59 remi-desktop org.gnome.Shell.desktop[1484]: xkbcommon: ERROR: Couldn't read rules file "/usr/share/X11/xkb/rules/evdev": Permission denied
Jul 16 17:09:59 remi-desktop org.gnome.Shell.desktop[1484]: xkbcommon: ERROR: No components returned from XKB rules "/usr/share/X11/xkb/rules/evdev"
Jul 16 17:09:59 remi-desktop org.gnome.Shell.desktop[1484]: xkbcommon: ERROR: Couldn't look up rules 'evdev', model 'pc105', layout 'us', variant '', options ''
Jul 16 17:09:59 remi-desktop audit[1484]: AVC avc:  denied  { map } for  pid=1484 comm="gnome-shell" path="/usr/share/X11/xkb/rules/evdev" dev="nvme0n1p3" ino=1243665 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0
Jul 16 17:09:59 remi-desktop audit[1484]: AVC avc:  denied  { map } for  pid=1484 comm="gnome-shell" path="/usr/share/X11/xkb/rules/evdev" dev="nvme0n1p3" ino=1243665 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0
Jul 16 17:09:59 remi-desktop audit[1484]: AVC avc:  denied  { map } for  pid=1484 comm="gnome-shell" path="/usr/share/X11/xkb/rules/evdev" dev="nvme0n1p3" ino=1243665 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file permissive=0
Jul 16 17:09:59 remi-desktop org.gnome.Shell.desktop[1484]: xkbcommon: ERROR: Couldn't read rules file "/usr/share/X11/xkb/rules/evdev": Permission denied
Jul 16 17:09:59 remi-desktop org.gnome.Shell.desktop[1484]: xkbcommon: ERROR: No components returned from XKB rules "/usr/share/X11/xkb/rules/evdev"
Jul 16 17:09:59 remi-desktop org.gnome.Shell.desktop[1484]: xkbcommon: ERROR: Couldn't look up rules 'evdev', model 'pc105+inet', layout 'us', variant '', options ''
Jul 16 17:09:59 remi-desktop org.gnome.Shell.desktop[1484]: xkbcommon: ERROR: Couldn't read rules file "/usr/share/X11/xkb/rules/evdev": Permission denied
Jul 16 17:09:59 remi-desktop org.gnome.Shell.desktop[1484]: xkbcommon: ERROR: No components returned from XKB rules "/usr/share/X11/xkb/rules/evdev"
Jul 16 17:09:59 remi-desktop org.gnome.Shell.desktop[1484]: xkbcommon: ERROR: Couldn't look up rules 'evdev', model 'pc105+inet', layout 'us', variant '', options ''
Jul 16 17:09:59 remi-desktop systemd-coredump[1550]: [🡕] Process 1484 (gnome-shell) of user 42 dumped core.
                                                     
                                                     Module libgvfscommon.so from rpm gvfs-1.50.5-1.fc38.x86_64
                                                     Module libgvfsdbus.so from rpm gvfs-1.50.5-1.fc38.x86_64
                                                     Module libdconfsettings.so from rpm dconf-0.40.0-8.fc38.x86_64
                                                     Module libedit.so.0 from rpm libedit-3.1-45.20221030cvs.fc38.x86_64
                                                     Module libdrm_nouveau.so.2 from rpm libdrm-2.4.114-2.fc38.x86_64
                                                     Module libdrm_amdgpu.so.1 from rpm libdrm-2.4.114-2.fc38.x86_64
                                                     Module libelf.so.1 from rpm elfutils-0.189-3.fc38.x86_64
                                                     Module libdrm_radeon.so.1 from rpm libdrm-2.4.114-2.fc38.x86_64
                                                     Module libsensors.so.4 from rpm lm_sensors-3.6.0-13.fc38.x86_64
                                                     Module iris_dri.so from rpm mesa-23.2.0-0.3.20230712.00.fb925c9.fc38.x86_64
                                                     Module libxshmfence.so.1 from rpm libxshmfence-1.3-12.fc38.x86_64
                                                     Module libxcb-sync.so.1 from rpm libxcb-1.13.1-11.fc38.x86_64
                                                     Module libxcb-present.so.0 from rpm libxcb-1.13.1-11.fc38.x86_64
                                                     Module libxcb-dri3.so.0 from rpm libxcb-1.13.1-11.fc38.x86_64
                                                     Module libwayland-client.so.0 from rpm wayland-1.22.0-1.fc38.x86_64
                                                     Module libxcb-xfixes.so.0 from rpm libxcb-1.13.1-11.fc38.x86_64
                                                     Module libxcb-dri2.so.0 from rpm libxcb-1.13.1-11.fc38.x86_64
                                                     Module libglapi.so.0 from rpm mesa-23.2.0-0.3.20230712.00.fb925c9.fc38.x86_64
                                                     Module libEGL_mesa.so.0 from rpm mesa-23.2.0-0.3.20230712.00.fb925c9.fc38.x86_64
                                                     Module libbrotlicommon.so.1 from rpm brotli-1.0.9-11.fc38.x86_64
                                                     Module libogg.so.0 from rpm libogg-1.3.5-5.fc38.x86_64
                                                     Module libvorbis.so.0 from rpm libvorbis-1.3.7-7.fc38.x86_64
                                                     Module libdatrie.so.1 from rpm libdatrie-0.2.13-5.fc38.x86_64
                                                     Module libicudata.so.72 from rpm icu-72.1-2.fc38.x86_64
                                                     Module libgmp.so.10 from rpm gmp-6.2.1-4.fc38.x86_64
                                                     Module libhogweed.so.6 from rpm nettle-3.8-3.fc38.x86_64
                                                     Module libnettle.so.8 from rpm nettle-3.8-3.fc38.x86_64
                                                     Module libtasn1.so.6 from rpm libtasn1-4.19.0-2.fc38.x86_64
                                                     Module libunistring.so.5 from rpm libunistring-1.1-3.fc38.x86_64
                                                     Module libidn2.so.0 from rpm libidn2-2.3.4-2.fc38.x86_64
                                                     Module libbrotlidec.so.1 from rpm brotli-1.0.9-11.fc38.x86_64
                                                     Module libbz2.so.1 from rpm bzip2-1.0.8-13.fc38.x86_64
                                                     Module libexpat.so.1 from rpm expat-2.5.0-2.fc38.x86_64
                                                     Module libevdev.so.2 from rpm libevdev-1.13.1-1.fc38.x86_64
                                                     Module libmtdev.so.1 from rpm mtdev-1.1.6-5.fc38.x86_64
                                                     Module libuuid.so.1 from rpm util-linux-2.38.1-4.fc38.x86_64
                                                     Module libxcb-xkb.so.1 from rpm libxcb-1.13.1-11.fc38.x86_64
                                                     Module libxcb-util.so.1 from rpm xcb-util-0.4.1-2.fc38.x86_64
                                                     Module libltdl.so.7 from rpm libtool-2.4.7-6.fc38.x86_64
                                                     Module libtdb.so.1 from rpm libtdb-1.4.8-1.fc38.x86_64
                                                     Module libvorbisfile.so.3 from rpm libvorbis-1.3.7-7.fc38.x86_64
                                                     Module libGLX.so.0 from rpm libglvnd-1.6.0-2.fc38.x86_64
                                                     Module libGLdispatch.so.0 from rpm libglvnd-1.6.0-2.fc38.x86_64
                                                     Module libxml2.so.2 from rpm libxml2-2.10.4-1.fc38.x86_64
                                                     Module libgraphite2.so.3 from rpm graphite2-1.3.14-11.fc38.x86_64
                                                     Module libthai.so.0 from rpm libthai-0.1.29-4.fc38.x86_64
                                                     Module libtinfo.so.6 from rpm ncurses-6.4-3.20230114.fc38.x86_64
                                                     Module libicuuc.so.72 from rpm icu-72.1-2.fc38.x86_64
                                                     Module libicui18n.so.72 from rpm icu-72.1-2.fc38.x86_64
                                                     Module libblkid.so.1 from rpm util-linux-2.38.1-4.fc38.x86_64
                                                     Module libseccomp.so.2 from rpm libseccomp-2.5.3-4.fc38.x86_64
                                                     Module libxkbregistry.so.0 from rpm libxkbcommon-1.5.0-2.fc38.x86_64
                                                     Module libgnutls.so.30 from rpm gnutls-3.8.0-2.fc38.x86_64
                                                     Module liblz4.so.1 from rpm lz4-1.9.4-2.fc38.x86_64
                                                     Module libzstd.so.1 from rpm zstd-1.5.5-1.fc38.x86_64
                                                     Module liblzma.so.5 from rpm xz-5.4.1-1.fc38.x86_64
                                                     Module libcap.so.2 from rpm libcap-2.48-6.fc38.x86_64
                                                     Module libp11-kit.so.0 from rpm p11-kit-0.24.1-6.fc38.x86_64

Sorry if it's something I missed and not a bug or incompatibility. I'm an eternal linux noob (configuring the keyboard took me a lot of time).

Another issue I'm not sure deserves a bug report: your website dreymar.colemak.org doesn't mention the key to activate the mouse is now TLDE, and not LSGT anymore.

And thank you for making this!

My keyboard configuration:

Option "XkbLayout" "us"
Option "XkbModel" "pc104aw-zqu"
Option "XkbVariant" "cmk_ed_us"
Option "XkbOptions" "misc:extend,lv5:caps_switch_lock,grp:shifts_toggle,compose:menu,keypad:pointerkeys,misc:cmk_curl_dh"

The \ key generates no symbol whatsoever

KeyPress event, serial 33, synthetic NO, window 0x2000001,
    root 0xf5, subw 0x0, time 30662205, (244,77), root:(261,482),
    state 0x0, keycode 51 (keysym 0x0, NoSymbol), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

xev output on \ keypress

Running the install-script fails on my machine with

@@@ install-dreymar-xmod.sh - ERROR: Local files copy error! @@@

This is both in the downloaded archive and when I clone. This happens because the shell scripts do not have executable permission in the tree.

It would be good to set the correct permissions for *.sh files to make it easier to install.

Hey!
I discovered Dvorak but wasn't very impressed, then I came accross Colemak and was very pleased.

It is very frustrating switching cold turkey so your little mod here will (I hope) help me make the transition.

Thanks!

I saw in the setxkb.sh script that it says NOTE: It now works with local xkb(-mod) dir, but I couldn't make it work. Can you please provide some guidance?

Thanks a lot!