#niri — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #niri, aggregated by home.social.
-
3 % di processore consumato
2 % di RAM impegnata
0 % di swap utilizzata
.
Il tutto con
#zenbrowser aperto e 15 schede;
#Kdenlive in modalità modifica;
#TELEGRAM e #twitch;
.
#cachios + #Niri + #DMS sono la risposta definitiva alla domanda definitiva sulle necessità hardware informatiche, finalmente il #Tiling piacevole anche per me. -
Did you know that #May25th isn't just a regular day, but International #TowelDay?
A must-have for any interstellar traveler! Because, as #DouglasAdams once said, a towel is the most useful thing you can have in the universe. So, whether you're #hitchhiking across the #galaxy or simply want to be well-prepared, don't forget your towel today!
And the ultimate question to the ultimate answer, at least as far as computing is concerned is @fedora 42 with #niri and #dms in #atomic distro -
Did you know that #May25th isn't just a regular day, but International #TowelDay?
A must-have for any interstellar traveler! Because, as #DouglasAdams once said, a towel is the most useful thing you can have in the universe. So, whether you're #hitchhiking across the #galaxy or simply want to be well-prepared, don't forget your towel today!
And the ultimate question to the ultimate answer, at least as far as computing is concerned is @fedora 42 with #niri and #dms in #atomic distro -
For fans of #Niri and #Hyprland folks who use the scrolling layout, what do you do to keep usage of the infinite canvas under control?
I find it easy to quickly accumulate an unmanagable number of windows offscreen.
Some ideas to mitigate this:
* Limit the canvas width to 2x the screen width.
* Devote part of the screen to showing a tiny view of what's accumulating off screen. -
Aparecen como las setas!
Wayle un shell de escritorio Wayland con la barra, notificaciones, OSD, fondos de pantalla y controles de dispositivo incorporados. Escrito en Rust con GTK4 y Relm4.Los módulos específicos de los compositores actualmente se dirigen a #Hyprland; el soporte de #niri, #Sway y #MangoWC está en desarrollo.
https://wayle.app/guide/getting-started -
Aparecen como las setas!
Wayle un shell de escritorio Wayland con la barra, notificaciones, OSD, fondos de pantalla y controles de dispositivo incorporados. Escrito en Rust con GTK4 y Relm4.Los módulos específicos de los compositores actualmente se dirigen a #Hyprland; el soporte de #niri, #Sway y #MangoWC está en desarrollo.
https://wayle.app/guide/getting-started -
Aparecen como las setas!
Wayle un shell de escritorio Wayland con la barra, notificaciones, OSD, fondos de pantalla y controles de dispositivo incorporados. Escrito en Rust con GTK4 y Relm4.Los módulos específicos de los compositores actualmente se dirigen a #Hyprland; el soporte de #niri, #Sway y #MangoWC está en desarrollo.
https://wayle.app/guide/getting-started -
Aparecen como las setas!
Wayle un shell de escritorio Wayland con la barra, notificaciones, OSD, fondos de pantalla y controles de dispositivo incorporados. Escrito en Rust con GTK4 y Relm4.Los módulos específicos de los compositores actualmente se dirigen a #Hyprland; el soporte de #niri, #Sway y #MangoWC está en desarrollo.
https://wayle.app/guide/getting-started -
Aparecen como las setas!
Wayle un shell de escritorio Wayland con la barra, notificaciones, OSD, fondos de pantalla y controles de dispositivo incorporados. Escrito en Rust con GTK4 y Relm4.Los módulos específicos de los compositores actualmente se dirigen a #Hyprland; el soporte de #niri, #Sway y #MangoWC está en desarrollo.
https://wayle.app/guide/getting-started -
Yeah, back to Fedora and Gnome. As nice as Cachy and Niri and Noctalia are, I just work too much with other RHEL systems daily to make this workflow change right now. It’s been a week and I’ve had so little time to even get basic things setup that just work out of the box in Fedora/gnome and elementaryOS/pantheon.
#CachyOS #fedora #elementaryos #niri #noctalia #gnome #pantheon
-
Yeah, back to Fedora and Gnome. As nice as Cachy and Niri and Noctalia are, I just work too much with other RHEL systems daily to make this workflow change right now. It’s been a week and I’ve had so little time to even get basic things setup that just work out of the box in Fedora/gnome and elementaryOS/pantheon.
#CachyOS #fedora #elementaryos #niri #noctalia #gnome #pantheon
-
Yeah, back to Fedora and Gnome. As nice as Cachy and Niri and Noctalia are, I just work too much with other RHEL systems daily to make this workflow change right now. It’s been a week and I’ve had so little time to even get basic things setup that just work out of the box in Fedora/gnome and elementaryOS/pantheon.
#CachyOS #fedora #elementaryos #niri #noctalia #gnome #pantheon
-
Yeah, back to Fedora and Gnome. As nice as Cachy and Niri and Noctalia are, I just work too much with other RHEL systems daily to make this workflow change right now. It’s been a week and I’ve had so little time to even get basic things setup that just work out of the box in Fedora/gnome and elementaryOS/pantheon.
#CachyOS #fedora #elementaryos #niri #noctalia #gnome #pantheon
-
Yeah, back to Fedora and Gnome. As nice as Cachy and Niri and Noctalia are, I just work too much with other RHEL systems daily to make this workflow change right now. It’s been a week and I’ve had so little time to even get basic things setup that just work out of the box in Fedora/gnome and elementaryOS/pantheon.
#CachyOS #fedora #elementaryos #niri #noctalia #gnome #pantheon
-
working from my #SurfaceGo 1 with a Pentium Gold CPU running #Fedora44 and #niri today instead of the usual #MacbookAir M1. Gods, I love this little machine so much. I prefer the form factor of a Surface over a Macbook anyday. The keyboard of the first Surface Go is soooo nice. It feels soooo good. I don't care if it is an underpowered machine. It is a loving machine.
I posted about it SIX YEARS AGO when I was running it and happy with Windows 10:
https://andregarzia.com/2020/01/a-year-with-the-surface-go.html
Now that I am finally running Linux on it, it became even better. So happy with this little guy. Just wish the battery would last longer. -
Spent a few hours tonight just trying to get the scaling to NOT be 125%. All the settings for #niri were set correctly to defaults at scaling factor of 1.
Looks like this is the same issue I have in Gnome where it picks up my resolution and automatically scales me up to 125%. Difference here is Gnome surfaces that setting in displays and you can quickly fix it. It is not surfaced as a setting anywhere to see in the cachy/niri settings.
I had to do the following and apparently I need to script this to do this every reboot as it’s not persistent. Shout out to a random forum post for the tidbit.
gsettings set org.gnome.desktop.interface scaling-factor 1
gsettings set org.gnome.desktop.interface text-scaling-factor 1.1
wlr-randr --output eDP-1 --scale 1So far I’m not actually hitting anything CachyOS specific and just getting used to Niri. I do like Niri so far. I need to tweak some settings (like getting to the app launcher via Super). I’m not sure if I like how many options there are so far though.
I’m not a UI ricer and enjoy the simplicity and sane defaults of #elementaryos and #gnome but I do have those on my main systems to fall back to while I play with this.
-
Yeah, this works for me with #fish and #niri:
1. Set fish_title to `pwd`.
2. Have a `ycwd` script:TITLE="$(niri msg --json focused-window | jq -r .title)"
if [ -d "$TITLE" ]; then
echo "$TITLE"
else
echo "$HOME"
fi3. Set the niri key binding: Mod+Return { spawn-sh "kitty -1 --working-directory=\"$(ycwd)\""; }
-
#dankmaterialshell die meisten Maschinen auf noctalia umgestellt.
Allerdings vermisse ich zwei Dinge:
- Desktop Widgets immer im Vordergrund - praktisch wenn man seine Tageszeitung im Vollbild-Modus liest und trotzdem noch die Uhrzeit einblenden kann
- Wetteranzeige ist bei dms viel detaillierter (stündlich). Bei noctalia hat man nur die tägliche Angabe. -
-
So I've decided to go with #CachyOS (again) for a while, this time testing out their default #MangoWC setup.
Which, I was surprised to learn, uses #DankLinux. So that was a pleasent discovery.
Anyway, so far so good. MangoWC isn't as flashy as Hyprland, but it's pretty enough, easy to configure, and the project isn't run by a transphobic shitheel.
The default keybinds aren't terrible, although I'm probably going to switch some around to be closer to my default #Niri setup. The install itself is quite minimal, without so much as a premade directory in ~/ (except /.local and /.config of course) and no GUI text editor (Neovim and Micro are preinstalled). I like being able to pick the one I want, so that was a big plus, actually.
The default file manager is #Nautilus (#Gnome Files), which took me by surprise, but it's a good choice with a strong feature set that blends into the minimalist aesthetic.
It defaults to #Firefox, but you can choose to leave it out at install and pacman in your favorite instead.
-
So I've decided to go with #CachyOS (again) for a while, this time testing out their default #MangoWC setup.
Which, I was surprised to learn, uses #DankLinux. So that was a pleasent discovery.
Anyway, so far so good. MangoWC isn't as flashy as Hyprland, but it's pretty enough, easy to configure, and the project isn't run by a transphobic shitheel.
The default keybinds aren't terrible, although I'm probably going to switch some around to be closer to my default #Niri setup. The install itself is quite minimal, without so much as a premade directory in ~/ (except /.local and /.config of course) and no GUI text editor (Neovim and Micro are preinstalled). I like being able to pick the one I want, so that was a big plus, actually.
The default file manager is #Nautilus (#Gnome Files), which took me by surprise, but it's a good choice with a strong feature set that blends into the minimalist aesthetic.
It defaults to #Firefox, but you can choose to leave it out at install and pacman in your favorite instead.
-
So I've decided to go with #CachyOS (again) for a while, this time testing out their default #MangoWC setup.
Which, I was surprised to learn, uses #DankLinux. So that was a pleasent discovery.
Anyway, so far so good. MangoWC isn't as flashy as Hyprland, but it's pretty enough, easy to configure, and the project isn't run by a transphobic shitheel.
The default keybinds aren't terrible, although I'm probably going to switch some around to be closer to my default #Niri setup. The install itself is quite minimal, without so much as a premade directory in ~/ (except /.local and /.config of course) and no GUI text editor (Neovim and Micro are preinstalled). I like being able to pick the one I want, so that was a big plus, actually.
The default file manager is #Nautilus (#Gnome Files), which took me by surprise, but it's a good choice with a strong feature set that blends into the minimalist aesthetic.
It defaults to #Firefox, but you can choose to leave it out at install and pacman in your favorite instead.
-
Solving the mystery of niri and swayidle—elogind
Based on the debug output from
swayidle, I started researching what the heckorg.freedesktop.login1.Managerwas doing. When usingsway, this was not used on my non-systemd system, andswayidleworks as expected.With
sway, the way it is working, from a casual user’s perspective:swayidleintercepts for an “idle state” message.swayidleruns the script that I have configured—swaylock-pluginlocks and the background is rotated continually.
Using
nirion my non-systemd system, there does seem to be this extra piece in the mix—logind. Or in my caseelogind.swayidleintercepts aPrepareForSleep signal...
-
Solving the mystery of niri and swayidle—elogind
Based on the debug output from
swayidle, I started researching what the heckorg.freedesktop.login1.Managerwas doing. When usingsway, this was not used on my non-systemd system, andswayidleworks as expected.With
sway, the way it is working, from a casual user’s perspective:swayidleintercepts for an “idle state” message.swayidleruns the script that I have configured—swaylock-pluginlocks and the background is rotated continually.
Using
nirion my non-systemd system, there does seem to be this extra piece in the mix—logind. Or in my caseelogind.swayidleintercepts aPrepareForSleep signal...
-
Solving the mystery of niri and swayidle—elogind
Based on the debug output from
swayidle, I started researching what the heckorg.freedesktop.login1.Managerwas doing. When usingsway, this was not used on my non-systemd system, andswayidleworks as expected.With
sway, the way it is working, from a casual user’s perspective:swayidleintercepts for an “idle state” message.swayidleruns the script that I have configured—swaylock-pluginlocks and the background is rotated continually.
Using
nirion my non-systemd system, there does seem to be this extra piece in the mix—logind. Or in my caseelogind.swayidleintercepts aPrepareForSleep signal...
-
Solving the mystery of niri and swayidle—elogind
Based on the debug output from
swayidle, I started researching what the heckorg.freedesktop.login1.Managerwas doing. When usingsway, this was not used on my non-systemd system, andswayidleworks as expected.With
sway, the way it is working, from a casual user’s perspective:swayidleintercepts for an “idle state” message.swayidleruns the script that I have configured—swaylock-pluginlocks and the background is rotated continually.
Using
nirion my non-systemd system, there does seem to be this extra piece in the mix—logind. Or in my caseelogind.swayidleintercepts aPrepareForSleep signal...
-
Debug output from swayidle on both sway and niri
I captured debug output from swayidle for a period time when using sway and then when using niri, which helped me understand a bit more of what’s going on. It seems that when running sway, I am getting idle state events at the expected intervals (300s), but when I am running niri, I am getting sleep events at unexpected intervals.
In a screen recording, niri almost immediately sent the sleep within 2 minutes!
The difference seems to be that swayidle is receiving property changes from
org.freedesktop.login1.Managerwhen using niri, but a simple "idle state" when using sway.I think I will start...
-
Debug output from swayidle on both sway and niri
I captured debug output from swayidle for a period time when using sway and then when using niri, which helped me understand a bit more of what’s going on. It seems that when running sway, I am getting idle state events at the expected intervals (300s), but when I am running niri, I am getting sleep events at unexpected intervals.
In a screen recording, niri almost immediately sent the sleep within 2 minutes!
The difference seems to be that swayidle is receiving property changes from
org.freedesktop.login1.Managerwhen using niri, but a simple "idle state" when using sway.I think I will start...
-
Debug output from swayidle on both sway and niri
I captured debug output from swayidle for a period time when using sway and then when using niri, which helped me understand a bit more of what’s going on. It seems that when running sway, I am getting idle state events at the expected intervals (300s), but when I am running niri, I am getting sleep events at unexpected intervals.
In a screen recording, niri almost immediately sent the sleep within 2 minutes!
The difference seems to be that swayidle is receiving property changes from
org.freedesktop.login1.Managerwhen using niri, but a simple "idle state" when using sway.I think I will start...
-
Debug output from swayidle on both sway and niri
I captured debug output from swayidle for a period time when using sway and then when using niri, which helped me understand a bit more of what’s going on. It seems that when running sway, I am getting idle state events at the expected intervals (300s), but when I am running niri, I am getting sleep events at unexpected intervals.
In a screen recording, niri almost immediately sent the sleep within 2 minutes!
The difference seems to be that swayidle is receiving property changes from
org.freedesktop.login1.Managerwhen using niri, but a simple "idle state" when using sway.I think I will start...