I was looking for a good generalist set of keybindings for my Steam Deck’s onboard controls that bound all the letter keys and also the necessary commands to navigate web pages and manipulate files. There isn’t any obvious layout to bind all the gamepad buttons, joysticks and touchpads to letter keys and keyboard commands/command chords, and further it feels like whatever solution you came up with would be impossible to memorize anyways.
Kind of a silly endeavor perhaps, but… touchscreen keyboards take up wayyyyy too much screen real estate on the Steam Deck, and further the pop up software keyboard sometimes doesn’t behave right with software that isn’t expecting a pop up touchscreen keyboard (i.e., not like a mobile app designed to handle one).
Then I randomly thought about Qutebrowser and vim keybindings… and I had an evil idea…
I want to try using this with neovim as well, and I thought y’all might get a kick out of it lol!
edit errr, oooff I don’t know how to get lemmy not to dump the text from my linked post completely unformated into this post
Yeah I used to be intimidated by the tiling no mouse thing. Then I took the dive, once I got the hang of it I can’t go back. Operating my system with one finger is just too tedious. With keyboard oriented and tiling it feels like operating my system with my mind via telepathy. I ran labwc for about 5 minutes before I logged out and went back to my sway environment.
Since I have an 28" 4K screen at home, I just prefer dragging windows around with the mouse. My laptop is a tiny, portable, 13 inch device with 1920x1080 pixels resolution so having a tiling WM there makes absolute sense. Since I use the laptop as literal laptop sometimes while on train, etc. not using the mouse to handle windows makes absolute sense to me.
I ran labwc for about 5 minutes before I logged out and went back to my sway environment.
I had the same first experience with it because it was/is mainly “advertised” as Openbox but for Wayland, and that you can reuse your Openbox configuration. Both is not correct. It is modeled after the box-look and supports some of Openbox’s features, but a lot of things are missing. You also cannot re-use most of your configuration without any changes.
A few weeks ago I took a deep breath and spent the weekend building a configuration from scratch. Now it works very well and is almost as usable as Openbox. The two “real” downsides I have are menu icons, which are category C (not in scope, so this won’t likely ever be implemented) and pipemenus, both are things that make up 95% of my Openbox menu setup. For icons I now use emojis and other Unicode characters and pipemenus well come with the next release.
