How’d you get the “not in your PATH” error message to display right? I get the weird “DBI connect” thing
I tried imv and hated it. I just use feh (through XWayland) or mpv now.
As if I needed more reasons to love Stephen Fry!
Fascinating! How’s it compare to youtube-tui? I’m really interested in starting to use a program like this… the YouTube website is so unbearably slow.
Catchy manifesto, perhaps, but the Yippies historically (to the extent there even was such a group) were the absolute pinnacle of spectacle for its own sake. They got nothing done, and ultimately served only to hurt the public image of the legitimate countercultural movements in the long term. I think it seriously goes against the more pragmatic and action-oriented outlook of Solarpunk to take cues from these guys.
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).
Yeah that’s a lot of what kept me out of most of home-manager’s functionality.
I will say, though, there are occasionally programs that have a lot of home-manager options yet few (if any) NixOS options (gammastep comes to mind), so I use it for those.
Also, configuring browsers with home-manager is fantastic!
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.
Help with swaywm window rules?
Fellas, I'm at my wit's end with this one. I'm trying to set a general rule for window opacity in sway, and then have a few programs excepted from it.
Back on i3 with picom, I could do this pretty easily by setting activeOpacity to 0.9, for example, and then specifying additional opacityRules like this:
"100:class_g = 'mpv'" "100:class_g = 'Brave-browser'"
Likewise, hyprland's window rules made it pretty easy to override the general opacity rules as well.
I can't seem to get this on sway, though; if I set it up like this:
```
[app_id=".*"] opacity 0.85
[app_id="brave_browser"] opacity set 1 [app_id="librewolf"] opacity 1 ``` it simply sets everything to 0.85.
Currently, I have this: ``` [app_id="^(?!mpv$|brave_browser$).*$"] opacity 0.85
[app_id="brave_browser"] opacity set 1
[app_id="mpv"] opacity 1
```
but it is still exhibiting the same behavior (except mpv also seems to totally disregard any opacity rules whatsoever).
Any help is greatly appreciated---I haven't been able to find anyone else asking or talking about what seems to me like pretty basic functionality.
How have I never heard of this! This is awesome!
Very cool. yabai is a great project that makes macOS actuallly usable.
Wow! Finally a niri user out in the wild! I’m super curious to hear about your experiences with it—do you find it to be stable enough for day to day use? What’s your workflow like? How’s it compare to what you’ve used before?
Yeah actually is there a way to NOT have nano on the system? I’d really like to remove it…
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.
Configuring Kakoune Bindings in the Helix Editor!
cross-posted from: https://lemmy.ml/post/15059157
> cross-posted from: https://lemmy.ml/post/15059150
>
> > Hey friends,
> >
> > I tried Kakoune for the first time recently—I definitely feel like it gets keybindings right.
> > So I just wrapped up configuring Helix to (as far as I can tell) use those bindings (basically, it totally cuts out select mode and makes things much faster).
> > Thought I'd share for anyone else interested.
> >
> > toml > > [keys.normal] > > H = "extend_char_left" > > J = "extend_line_down" > > K = "extend_line_up" > > L = "extend_char_right" > > > > W = "extend_next_word_start" > > E = "extend_next_word_end" > > B = "extend_prev_word_start" > > > > A-j = "join_selections" > > > > A-n = "search_prev" > > N = "extend_search_next" > > A-N = "extend_search_prev" > > > > [keys.normal.g] > > e = ["goto_last_line", "goto_line_end"] > > G = ["select_mode", "goto_file_start", "normal_mode"] > > [keys.normal.G] > > H = "extend_to_line_start" > > L = "extend_to_line_end" > > E = ["select_mode", "goto_last_line", "goto_line_end", "normal_mode"] > > [keys.normal.v] > > t = "align_view_top" > > b = "align_view_bottom" > > v = "align_view_center" > >
> > Happy editing!
Kakoune Bindings in Helix (Guide)
cross-posted from: https://lemmy.ml/post/15059150
> Hey friends,
>
> I tried Kakoune for the first time recently—I definitely feel like it gets keybindings right.
> So I just wrapped up configuring Helix to (as far as I can tell) use those bindings (basically, it totally cuts out select mode and makes things much faster).
> Thought I'd share for anyone else interested.
>
> toml > [keys.normal] > H = "extend_char_left" > J = "extend_line_down" > K = "extend_line_up" > L = "extend_char_right" > > W = "extend_next_word_start" > E = "extend_next_word_end" > B = "extend_prev_word_start" > > A-j = "join_selections" > > A-n = "search_prev" > N = "extend_search_next" > A-N = "extend_search_prev" > > [keys.normal.g] > e = ["goto_last_line", "goto_line_end"] > G = ["select_mode", "goto_file_start", "normal_mode"] > [keys.normal.G] > H = "extend_to_line_start" > L = "extend_to_line_end" > E = ["select_mode", "goto_last_line", "goto_line_end", "normal_mode"] > [keys.normal.v] > t = "align_view_top" > b = "align_view_bottom" > v = "align_view_center" >
> Happy editing!
Kakoune Bindings in Helix (Guide)
Hey friends,
I tried Kakoune for the first time recently—I definitely feel like it gets keybindings right. So I just wrapped up configuring Helix to (as far as I can tell) use those bindings (basically, it totally cuts out select mode and makes things much faster). Thought I'd share for anyone else interested.
```toml [keys.normal] H = "extend_char_left" J = "extend_line_down" K = "extend_line_up" L = "extend_char_right"
W = "extend_next_word_start" E = "extend_next_word_end" B = "extend_prev_word_start"
A-j = "join_selections"
A-n = "search_prev" N = "extend_search_next" A-N = "extend_search_prev"
[keys.normal.g] e = ["goto_last_line", "goto_line_end"] G = ["select_mode", "goto_file_start", "normal_mode"] [keys.normal.G] H = "extend_to_line_start" L = "extend_to_line_end" E = ["select_mode", "goto_last_line", "goto_line_end", "normal_mode"] [keys.normal.v] t = "align_view_top" b = "align_view_bottom" v = "align_view_center" ``` Happy editing!
Question about Xfce vs. MATE
Fellas,
I've been using my current setup on NixOS (Xfce + i3) for about a month now---it's totally great, but I've got some minor things that bother me just a little bit, and I want to see if Wayland does anything for me. I like my combination of a lightweight desktop and tiling windows, so I thought maybe I could do something like MATE + Sway?
Does anyone run anything like this? MATE seems pretty close to Xfce, right?
Happy to hear any thoughts.
Cheers!