3 ms·
So I have very mixed feelings. On the one hand, super cool; this is the first time in a long time I've actually considered switching away from i3, because this
by yjftsjthsd-h 5y ago
So I have very mixed feelings. On the one hand, super cool; this is the first time in a long time I've actually considered switching away from i3, because this seems like a natural fit for how I actually want to work. On the other hand, Wayland decided that each and every compositor is responsible for everything, so AFAICT cardboard can only handle QWERTY right now, and that's a complete non-starter for me.
- boogerlad 5y agoWhere do you see that Cardboard handles only QWERTY?
- yjftsjthsd-h 5y agoEr, on my laptop? It might be more precise to say that I can't find any way to make it use anything else; manpages give me nothing, grepping for "layout" in the source tree gives me nothing (relevant; window layouts show up), and there's an open issue (https://gitlab.com/cardboardwm/cardboard/-/issues/30 https://gitlab.com/cardboardwm/cardboard/-/issues/30) asking for it, all of which makes me conclude that it doesn't appear to support doing anything but QWERTY. That said, I said "AFAICT" for a reason; if you can prove me wrong I'll be quite grateful (because, seriously, I would like to use this thing).
- boogerlad 5y agoOh I think I understand what you're saying now. You have a laptop with a QWERTY hardware layout, and rely on the WM to remap the keys to a different layout? Sorry I can't help out. Just wanted to understand the issue.
- yjftsjthsd-h 5y agoBasically, yes. The hardware is QWERTY, and something in software has to be fiddled with to get my preferred layout - on Linux console that's loadkeys, in X11 it's setxkbmap or a config file, other systems do their own thing. The annoying thing to me is that in X11, the X server (usually Xorg) was the single point of configuration, and setxkbmap would work with any window manager without any special support needed; in Wayland, the compositor replaces Xorg and the window manager, so every single compositor has to do its own support for changing keyboard layout. As a sibling comment notes, wlroots appears to make this easier to implement, but as far as I can make out (I'm not much of a programmer) the dev still has to actually wire it up to do that, and cardboard doesn't seem to have done so. In the general case, I'm annoyed because the end result is that even if everyone did implement it, every single compositor would have its own special setting, when before I could either run setxkbmap or set it in the Xorg configuration file and it would work regardless of what window manager I happened to be running today.
- zucker42 5y agoCardboard uses wlroots.
- yjftsjthsd-h 5y agoAnd it looks like that makes it easier for the devs to support switching layouts, but AFAICT wlroots doesn't directly expose anything I can tweak as a user. I tried searching the web, hoping it read an environment variable or such, but couldn't find anything. Did I miss something? (And as a general comment, even if wlroots did make this uniformly work, that only helps for compositors that use wlroots; with X, I could just tell the X server to switch layouts and it would work with every single window manager in existence.)
- feanaro 5y agoWell that just means wlroots is the standard in the sense you had with X, not Wayland. I too consider this unfortunate and a weird design choice, but at least we have this option on stabilizing on wlroots and ignoring everything else as something completely separate.