![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/q98XK4sKtw.png)
As if I needed more reasons to love Stephen Fry!
As if I needed more reasons to love Stephen Fry!
What’s that tablet it’s running on?
This is awesome! Thank you!
These look great!
I’d personally be curious, though, to experiment with non-standard input and UI designs on these phones. Although the touchscreen model has become standard, I’m not sure it’s ultimately the best for all things—I’ve been deeply enjoying my Garmin watch, for example, which has four buttons rather than a touchscreen. I think buttons, dials, etc., (besides simply feeling good to use) are faster for some things. If we’re gonna go against the grain, why not go crazy? I think physical buttons (or at least stuff like the back button on Android) may be to touchscreen interfaces what keyboard-centric workflows are to the mouse and GUI (in terms of efficiency).
I guess I should have written the post a bit more clearly.
I’ve got the for_window
part, it’s just that after I set the opacity for all windows app_id=.*
, the following lines of the config cannot override that for the specific windows I want different opacities for.
How have I never heard of this! This is awesome!
Very cool. yabai
is a great project that makes macOS actuallly usable.
The best way to understand really is to install both and try yourself, but basically I would say Kakoune is more “radical” than Helix, which feels more like Vim. Both move the selection in normal mode, but Helix has you extend it using what’s basically visual mode, whereas Kakoune cuts out visual mode altogether and has you hold Shift. As you can see in the config, reconfiguring what Shift does causes issues with normal Vim bindings (like joining selections with J), so Kakoune solves this with Alt.
After using it for a few days, it made a lot of sense to my brain—I would say, in general, Kakoune feels enormously well thought-out and carefully considered in every element of its design.
P.S—
My main problem is screen tearing (my display refresh seems to be 59.999, and I notice this when moving windows around or watching 60 FPS video or even just scrolling PDFs)—is that something Wayland would even help at all? Am I just wasting my time here?
Keeping my fingers crossed for XFCE…🤞
Good question, I don’t know! I haven’t touched a Chromebook since at least 2020…
If I were to do it now, I’d probably still use crouton, but get it to download something other than Ubuntu 16.04, or I’d just dual boot.
I did this back in the day! The tool of choice as the time was crouton, because it came with a keybinding that let us stealthily switch back to the ChromeOS desktop whenever the teacher walked by :)
My first ever Linux experience was with the crouton project on a Chromebook in school (Ubuntu 16.04). A buddy of mine figured it out and we all wanted to play Minecraft during class. Thing is, I ended up enjoying tinkering with the OS as much as I did playing Minecraft… so now I’m stuck trying to learn NixOS.
I tried
imv
and hated it. I just usefeh
(through XWayland) ormpv
now.