Everything I read says it’s a feature enabled in what ever compositor you choose, if your compositor supports it. Why isn’t there a general purpose keybinding program like setxkbmap? Does it just not exist yet or must it be built into the compositor?
I’ve read [this stackexchange thread] on something related but it all seems to be using XKB which should imply I’m using XWayland?
How is NixOS on a Chromebook? The Chromebook I’ve been hacking on exists as a beater for trying environments without disrupting the (principally Arch+KDE on X) boxes I do my real work on, and I was thinking about trying Nix on it, but it seemed like the combination of 16GB eMMC and Nix’s propensity for large disc usage would make that difficult.
Yeah, that ain’t gonna work.
On my chromebook, it runs great. But I have a 128gb ssd. The only things that don’t work are hdmi audio and automatically switching from speakers to the audio jack.
As expected from the docs, that’s why I was surprised to see you mention Nix on a Chromebook, it seemed like order of magnitude wrong. 128GB is an unusual amount of local storage for a Chromebook.
I have a little Arch/Hyprland install that fits a comfortable environment in like 8 of the 16GB in my Dell 3189 right now - It was kind of a fun project fitting it and chasing down all the little annoyances, I think it all works now other than the lack of pluming to make use of the fold sensors, and an occasional ASoC bug for which patches have landed upstream in Linux or Pipewire since the last releases.