Of course... I'm using a japanese Happy Hacking Keyboard Pro JP (HHKB Pro JP). The HHKB is kinda famous for its Topre switches: I'm just using the japanese variant. They're kinda pricey as far as keyboards but the price is okay'ish if you buy them directly in Japan.
Before using a japanese HHKB Pro JP I was using a reqular US QWERTY HHKB Pro 2. But then I figured out a narrower spacebar and more modifiers would suit me best. The big enter key on the HHKB Pro JP may not be for everyone that said.
As for the setup, I don't have a public Github page with my config (I use Git but with bare git repos on my own servers) and it's actually going to depend on how you did configure the DIP switches on the HHKB Pro JP (it's got 6 dip switches IIRC) but it's nothing out of the ordinary.
I'll just throw random infos that may get you started if you go this route...
I'm on Linux so it's just one .xkb file which is mostly a modified QWERTY layout to add Hyper and Super modifiers. I had to mess up a bit with the japanese Henkan and Muhenkan modifiers keycodes IIRC.
As a sidenote I'll say that you probably can do everything from the .xkb file but xkb and xmodmap (to set up modifiers) aren't mutually exclusive.
In the .xbk file a "regular" key like, say, 'x' stays of the type ALPHABETIC but I modified i j k and l to be FOUR_ALPHA and they're then (example for 'i'):
key <AD08> { type= "FOUR_ALPHA", symbols[Group1]= [ i, I, osfUp, osfUp ] };
where FOUR_ALPHA has "Hyper" in its short modifiers list.
I use Hyper for a lot of shortcuts (I configured Hyper to be the key at the left of the spacebar) but not for ijkl: Hyper+ijkl is used to send arrow keys code, always.
As for Super I use it only for my WM: so I configured one key to be Super in .xkb and then my WM (Awesome WM) only requires one line to be modified to tell it which modifier you want to use for shortcuts.
It's not complicated but it took me some time to set up everything: mostly because I had no idea how the .xkb file format was working and it certainly looks a bit alien.
I versioned my .xkb keymap files in Git and I experimented. I'm still under X so an xev window open to see the event (not sure how that works under Wayland) / keycodes sent, an editor to edit the .xkb file, commit changes as soon as good progress were made:
Before using a japanese HHKB Pro JP I was using a reqular US QWERTY HHKB Pro 2. But then I figured out a narrower spacebar and more modifiers would suit me best. The big enter key on the HHKB Pro JP may not be for everyone that said.
As for the setup, I don't have a public Github page with my config (I use Git but with bare git repos on my own servers) and it's actually going to depend on how you did configure the DIP switches on the HHKB Pro JP (it's got 6 dip switches IIRC) but it's nothing out of the ordinary.
I'll just throw random infos that may get you started if you go this route...
I'm on Linux so it's just one .xkb file which is mostly a modified QWERTY layout to add Hyper and Super modifiers. I had to mess up a bit with the japanese Henkan and Muhenkan modifiers keycodes IIRC.
As a sidenote I'll say that you probably can do everything from the .xkb file but xkb and xmodmap (to set up modifiers) aren't mutually exclusive.
In the .xbk file a "regular" key like, say, 'x' stays of the type ALPHABETIC but I modified i j k and l to be FOUR_ALPHA and they're then (example for 'i'):
where FOUR_ALPHA has "Hyper" in its short modifiers list.I use Hyper for a lot of shortcuts (I configured Hyper to be the key at the left of the spacebar) but not for ijkl: Hyper+ijkl is used to send arrow keys code, always.
As for Super I use it only for my WM: so I configured one key to be Super in .xkb and then my WM (Awesome WM) only requires one line to be modified to tell it which modifier you want to use for shortcuts.
It's not complicated but it took me some time to set up everything: mostly because I had no idea how the .xkb file format was working and it certainly looks a bit alien.
I versioned my .xkb keymap files in Git and I experimented. I'm still under X so an xev window open to see the event (not sure how that works under Wayland) / keycodes sent, an editor to edit the .xkb file, commit changes as soon as good progress were made:
To test the new settings. Rinse and repeat.Once it's set up, it's set up for good.