You are not logged in.
Pages: 1
I recently switched to Sway, the process of which cascaded into running as much as possible on my machine through Wayland. I compiled everything I discovered and configured into this guide.
To give you a sample, the following are now running completely through Wayland on my machine: Sway itself, Waybar, the Wofi app launcher, browsers (and screen sharing), Emacs, all GTK apps, and most QT apps. I worked through some gotchas with Steam and Input Methods too. Overall things are much "snappier" and I'm quite happy with the result!
Please enjoy the guide, and do let me know if you notice any issues. Cheers!
Author of Aura
Offline
Interesting , a few comments :
- Maybe add sway to the title ?
- clarifying which parts are sway specific and which are valid for wayland in general would improve readability .
- Technically wayland is a display server protocol and doesn't have a concept of window managers .
Maybe you can use the description archlinux uses for sway package ?
$ pacman -Si sway | grep Description
Description : Tiling Wayland compositor and replacement for the i3 window manager
$
- Several of the solutions / workarounds look like they come from other sources like archwiki .
If that's correct, could you add links to those sources ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Great guide! I followed this over the weekend to successfully get Wayland and Sway up and running. Thanks.
Offline
Coincidence! I was hacking my own sway config in the last weeks without knowing your guide, and got pretty similar results.
Regarding emacs, I use this one because I prefer self compiling and want native code compilation for elisp files
I read somethig about xeyes, but your guide was the first one which told me everything to know abot how to use it for this purpose. But for cli enthusiasts, here is what I do:
swaymsg -t get_tree | grep -A4 -B0 app_id
"app_id": "Alacritty",
"visible": true,
"max_render_time": 0,
"shell": "xdg_shell",
"inhibit_idle": false,
--
"app_id": null,
"visible": false,
"max_render_time": 0,
"shell": "xwayland",
"inhibit_idle": false,
--
"app_id": "python3",
"visible": false,
"max_render_time": 0,
"shell": "xdg_shell",
"inhibit_idle": false,
--
"app_id": "emacs",
"visible": false,
"max_render_time": 0,
"shell": "xdg_shell",
"inhibit_idle": false,
will show me the programms runnig natively under wayland, and that one program (in this example) is not. To find the one which is not, I can use
swaymsg -t get_tree | grep -A 4 -B 0 class
"class": "Fotoxx",
"instance": "fotoxx",
"title": "Fotoxx 470\/621 \/home\/haawda\/Desktop\/ciggypiggy\/Bilder\/ 24_250614n0214.jpg (undated)",
"transient_for": null,
"window_type": "normal"
Random wallpapers: I do not use another seperate application for this, but an alias. I do not store my wallpapers in a seperate directory, but have file swaypool including the full paths.
swaypool:
/home/haawda/Desktop/ciggypiggy/Bilder/251017n4_8x5/25_261017n0032.jpg
/home/haawda/Desktop/Bilder/j/jones/sarah/2020-04-21-194301_8x5.jpg
/home/haawda/Desktop/Bilder/unbekannt/holding/5/2166_8x5.jpg
/home/haawda/Desktop/ciggypiggy/Bilder/240613n1_8x5/240613n0004.JPG
/home/haawda/Desktop/Bilder/r/RikeSchmidt_01_8x5.jpg
/home/haawda/Desktop/Bilder/l/leroy-beaulieu/0022_8x5.jpg
/home/haawda/Desktop/ciggypiggy/Bilder/div/040120n0083_8x5.jpg
Alias:
alias wcs='while read line ; do swaybg -o "*" -i $line -m fill; sleep 20;killall swaybg; done < swaypool&
Last edited by Stefan Husmann (2021-03-15 17:46:57)
Offline
Pages: 1