![](/static/253f0d9/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?
Reminds me of John F. Hickory…
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).
Hey friend,
My recommendation is to keep things dead simple as you start out—no fancy channels or flake inputs and such, at least not where not necessary. I’ve found a lot of success in going slow, and not feeling rushed to do everything the NixOS way at first (for example, I still manage my dotfiles with GNU stow
instead of home-manager). I started off with a very simple flake and basically just using my configuration.nix to declare packages, gradually learning more from there. The Nix ecosystem is as extremely powerful as it is poorly documented—it unfortunately sometimes takes a while to (as you’ve noted) even just find information.
I’ve linked below two sites I found unbelievably helpful in my journey—the first one helps you get up and running with a very simple flake (and, yes, you will want to use a flake, even if it isn’t obvious right now why), and the second one is a huge search engine of all NixOS options, the first place I check when I’m putting something new on my system.
Good luck!
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.
Yeah actually is there a way to NOT have nano on the system? I’d really like to remove it…
Always nice to see Helix :)
I think it’s possible to remap Helix to be almost (if not completely) Vim-like. I got it to be (I think completely) Kakoune-like with like 15 lines in my config.
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.
I was able to go zero to Nix in probably 6-10 hours, and could’ve done it sooner if I’d known about this sooner (and I’m not a super technical person).
Tablet?
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?
FreeBSD has rollbacks like Nix?
Grass. He’s outside. He’s escaped the computer.
I tried
imv
and hated it. I just usefeh
(through XWayland) ormpv
now.