#sway — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #sway, aggregated by home.social.
-
Ich nutze seit vielen Jahren den Font "Terminus" in der OTB-Variante für meine Terminals - xterm unter Xorg und #foot unter #Sway .
Nun setzen viele Distros nach und nach als Default die Konfiguration, Bitmap-Fonts zu "verbieten", zuletzt #Void Linux. Klar kann man das wieder deaktivieren, aber es könnte sein, dass die Bitmap-Fonts irgendwann endgültig verschwinden.
Das Problem ist: Im Bereich der skalierbaren Fonts (TTF u.ä.) habe ich bisher keinen gleichartigen Ersatz gefunden. "Hack", "IosevkaTerm" und wie sie alle heißen - alle sehen sie im Vergleich zu den Terminus OTB Fonts "schwammig" und unscharf aus.
-
Ich nutze seit vielen Jahren den Font "Terminus" in der OTB-Variante für meine Terminals - xterm unter Xorg und #foot unter #Sway .
Nun setzen viele Distros nach und nach als Default die Konfiguration, Bitmap-Fonts zu "verbieten", zuletzt #Void Linux. Klar kann man das wieder deaktivieren, aber es könnte sein, dass die Bitmap-Fonts irgendwann endgültig verschwinden.
Das Problem ist: Im Bereich der skalierbaren Fonts (TTF u.ä.) habe ich bisher keinen gleichartigen Ersatz gefunden. "Hack", "IosevkaTerm" und wie sie alle heißen - alle sehen sie im Vergleich zu den Terminus OTB Fonts "schwammig" und unscharf aus.
-
Ich nutze seit vielen Jahren den Font "Terminus" in der OTB-Variante für meine Terminals - xterm unter Xorg und #foot unter #Sway .
Nun setzen viele Distros nach und nach als Default die Konfiguration, Bitmap-Fonts zu "verbieten", zuletzt #Void Linux. Klar kann man das wieder deaktivieren, aber es könnte sein, dass die Bitmap-Fonts irgendwann endgültig verschwinden.
Das Problem ist: Im Bereich der skalierbaren Fonts (TTF u.ä.) habe ich bisher keinen gleichartigen Ersatz gefunden. "Hack", "IosevkaTerm" und wie sie alle heißen - alle sehen sie im Vergleich zu den Terminus OTB Fonts "schwammig" und unscharf aus.
-
Ich nutze seit vielen Jahren den Font "Terminus" in der OTB-Variante für meine Terminals - xterm unter Xorg und #foot unter #Sway .
Nun setzen viele Distros nach und nach als Default die Konfiguration, Bitmap-Fonts zu "verbieten", zuletzt #Void Linux. Klar kann man das wieder deaktivieren, aber es könnte sein, dass die Bitmap-Fonts irgendwann endgültig verschwinden.
Das Problem ist: Im Bereich der skalierbaren Fonts (TTF u.ä.) habe ich bisher keinen gleichartigen Ersatz gefunden. "Hack", "IosevkaTerm" und wie sie alle heißen - alle sehen sie im Vergleich zu den Terminus OTB Fonts "schwammig" und unscharf aus.
-
أطلق مطورو برنامج Sway الإصدار الجديد 1.12 من مدير النوافذ الشهير لمنصة Wayland، والذي يقدم ميزات متقدمة مثل إمكانية تسجيل نوافذ التطبيقات بشكل فردي، ودعم تقنية HDR10 للشاشات المتوافقة باستخدام محرك Vulkan. كما يتضمن التحديث دعم بروتوكولات Wayland الجديدة لإدارة الألوان ومساحات العمل، ويتطلب الآن مكتبة wlroots 0.20.0 للتشغيل. علاوة على ذلك، تم تحسين إدارة الألوان وإضافة اختصارات للتحكم بالوسائط، مع تسهيل عملية الإقلاع على معالجات الرسوميات غير المدعومة.
-
#Sway 1.12 #Wayland Compositor Released with HDR10 Support via #Vulkan Renderer and Many Other New Features https://9to5linux.com/sway-1-12-wayland-compositor-released-with-hdr10-support-via-vulkan-renderer
-
#Sway 1.12 #Wayland Compositor Released with HDR10 Support via #Vulkan Renderer and Many Other New Features https://9to5linux.com/sway-1-12-wayland-compositor-released-with-hdr10-support-via-vulkan-renderer
-
#Sway 1.12 #Wayland Compositor Released with HDR10 Support via #Vulkan Renderer and Many Other New Features https://9to5linux.com/sway-1-12-wayland-compositor-released-with-hdr10-support-via-vulkan-renderer
-
#Sway 1.12 #Wayland Compositor Released with HDR10 Support via #Vulkan Renderer and Many Other New Features https://9to5linux.com/sway-1-12-wayland-compositor-released-with-hdr10-support-via-vulkan-renderer
-
#Sway 1.12 #Wayland Compositor Released with HDR10 Support via #Vulkan Renderer and Many Other New Features https://9to5linux.com/sway-1-12-wayland-compositor-released-with-hdr10-support-via-vulkan-renderer
-
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 -
After a bit on #Gnome, I am finding my way back to #Sway... Nvidia drivers must be working better, as Sway isn't crashing like it used to.
I managed to get Gnome somewhat transformed into a an #i3 / sway like experience, but it wasn't quite the same. Setting up sway again, I realize how much "in the way" the "windows like" VM's like Gnome / #KDE / #Cosmic end up.
The simpler tiling managers are a tad more pain to configure / get used to, but the payoff is a fast, tailored, keyboard focused computer experience.
I had to force myself to use i3 for several days to get used to the difference, but that paid off.
Things seem to work better when the applications get more focus and the desktop is... not really much of a thing.
-
After a bit on #Gnome, I am finding my way back to #Sway... Nvidia drivers must be working better, as Sway isn't crashing like it used to.
I managed to get Gnome somewhat transformed into a an #i3 / sway like experience, but it wasn't quite the same. Setting up sway again, I realize how much "in the way" the "windows like" VM's like Gnome / #KDE / #Cosmic end up.
The simpler tiling managers are a tad more pain to configure / get used to, but the payoff is a fast, tailored, keyboard focused computer experience.
I had to force myself to use i3 for several days to get used to the difference, but that paid off.
Things seem to work better when the applications get more focus and the desktop is... not really much of a thing.
-
After a bit on #Gnome, I am finding my way back to #Sway... Nvidia drivers must be working better, as Sway isn't crashing like it used to.
I managed to get Gnome somewhat transformed into a an #i3 / sway like experience, but it wasn't quite the same. Setting up sway again, I realize how much "in the way" the "windows like" VM's like Gnome / #KDE / #Cosmic end up.
The simpler tiling managers are a tad more pain to configure / get used to, but the payoff is a fast, tailored, keyboard focused computer experience.
I had to force myself to use i3 for several days to get used to the difference, but that paid off.
Things seem to work better when the applications get more focus and the desktop is... not really much of a thing.
-
After a bit on #Gnome, I am finding my way back to #Sway... Nvidia drivers must be working better, as Sway isn't crashing like it used to.
I managed to get Gnome somewhat transformed into a an #i3 / sway like experience, but it wasn't quite the same. Setting up sway again, I realize how much "in the way" the "windows like" VM's like Gnome / #KDE / #Cosmic end up.
The simpler tiling managers are a tad more pain to configure / get used to, but the payoff is a fast, tailored, keyboard focused computer experience.
I had to force myself to use i3 for several days to get used to the difference, but that paid off.
Things seem to work better when the applications get more focus and the desktop is... not really much of a thing.
-
After a bit on #Gnome, I am finding my way back to #Sway... Nvidia drivers must be working better, as Sway isn't crashing like it used to.
I managed to get Gnome somewhat transformed into a an #i3 / sway like experience, but it wasn't quite the same. Setting up sway again, I realize how much "in the way" the "windows like" VM's like Gnome / #KDE / #Cosmic end up.
The simpler tiling managers are a tad more pain to configure / get used to, but the payoff is a fast, tailored, keyboard focused computer experience.
I had to force myself to use i3 for several days to get used to the difference, but that paid off.
Things seem to work better when the applications get more focus and the desktop is... not really much of a thing.
-
Si vous utilisez Niri/Sway ou tout autre gestionnaire de fenêtres pour Wayland et que vous souhaitez activer/désactiver des écrans quand vous les branchez, Kanshi est fait pour vous : https://github.com/emersion/kanshi
-
Si vous utilisez Niri/Sway ou tout autre gestionnaire de fenêtres pour Wayland et que vous souhaitez activer/désactiver des écrans quand vous les branchez, Kanshi est fait pour vous : https://github.com/emersion/kanshi
-
Si vous utilisez Niri/Sway ou tout autre gestionnaire de fenêtres pour Wayland et que vous souhaitez activer/désactiver des écrans quand vous les branchez, Kanshi est fait pour vous : https://github.com/emersion/kanshi
-
TileOS 2.0 aggiorna la base a Debian 13, migliora Wayland e introduce nuove edizioni sperimentali con Niri e MiracleWM. #Linux #TileOS #Debian13 #Wayland #Sway #OpenSource #LinuxDesktop
-
TileOS 2.0 aggiorna la base a Debian 13, migliora Wayland e introduce nuove edizioni sperimentali con Niri e MiracleWM. #Linux #TileOS #Debian13 #Wayland #Sway #OpenSource #LinuxDesktop
-
TileOS 2.0 aggiorna la base a Debian 13, migliora Wayland e introduce nuove edizioni sperimentali con Niri e MiracleWM. #Linux #TileOS #Debian13 #Wayland #Sway #OpenSource #LinuxDesktop
-
TileOS 2.0 aggiorna la base a Debian 13, migliora Wayland e introduce nuove edizioni sperimentali con Niri e MiracleWM. #Linux #TileOS #Debian13 #Wayland #Sway #OpenSource #LinuxDesktop
-
TileOS 2.0 aggiorna la base a Debian 13, migliora Wayland e introduce nuove edizioni sperimentali con Niri e MiracleWM. #Linux #TileOS #Debian13 #Wayland #Sway #OpenSource #LinuxDesktop
-
Finally fixed #dmenu to launch scripts from my `~/bin` correctly.
The issue is that my home directory is an import from my previous Pop!OS install, but currently running on CachyOS, and there's some differences of implicit assumptions between the two. The short version is that I was missing a `~/.xsession` file containing:
```
#!/bin/sh
. ~/.profile
```I already had a `~/.profile` that worked correctly, but it wasn't being executed during X11 login, so I had the system default `$PATH` but nothing user-specific. I also needed to delete my `~/.cache/dmenu_run` so it would recompute my path-available executables. Now I can properly launch Zen browser, and a wrapped version of Signal that actually uses the correct credential wallet, when using #i3.
I'll probably have to figure out similar fuckery again if I ever get #sway to work on my graphics card.
-
Finally fixed #dmenu to launch scripts from my `~/bin` correctly.
The issue is that my home directory is an import from my previous Pop!OS install, but currently running on CachyOS, and there's some differences of implicit assumptions between the two. The short version is that I was missing a `~/.xsession` file containing:
```
#!/bin/sh
. ~/.profile
```I already had a `~/.profile` that worked correctly, but it wasn't being executed during X11 login, so I had the system default `$PATH` but nothing user-specific. I also needed to delete my `~/.cache/dmenu_run` so it would recompute my path-available executables. Now I can properly launch Zen browser, and a wrapped version of Signal that actually uses the correct credential wallet, when using #i3.
I'll probably have to figure out similar fuckery again if I ever get #sway to work on my graphics card.
-
Finally fixed #dmenu to launch scripts from my `~/bin` correctly.
The issue is that my home directory is an import from my previous Pop!OS install, but currently running on CachyOS, and there's some differences of implicit assumptions between the two. The short version is that I was missing a `~/.xsession` file containing:
```
#!/bin/sh
. ~/.profile
```I already had a `~/.profile` that worked correctly, but it wasn't being executed during X11 login, so I had the system default `$PATH` but nothing user-specific. I also needed to delete my `~/.cache/dmenu_run` so it would recompute my path-available executables. Now I can properly launch Zen browser, and a wrapped version of Signal that actually uses the correct credential wallet, when using #i3.
I'll probably have to figure out similar fuckery again if I ever get #sway to work on my graphics card.
-
Finally fixed #dmenu to launch scripts from my `~/bin` correctly.
The issue is that my home directory is an import from my previous Pop!OS install, but currently running on CachyOS, and there's some differences of implicit assumptions between the two. The short version is that I was missing a `~/.xsession` file containing:
```
#!/bin/sh
. ~/.profile
```I already had a `~/.profile` that worked correctly, but it wasn't being executed during X11 login, so I had the system default `$PATH` but nothing user-specific. I also needed to delete my `~/.cache/dmenu_run` so it would recompute my path-available executables. Now I can properly launch Zen browser, and a wrapped version of Signal that actually uses the correct credential wallet, when using #i3.
I'll probably have to figure out similar fuckery again if I ever get #sway to work on my graphics card.
-
-
-
-
Oh wow, it works in #Sway, too!
-
Oh wow, it works in #Sway, too!
-
Oh wow, it works in #Sway, too!
-
Oh wow, it works in #Sway, too!
-
Oh wow, it works in #Sway, too!
