desktop-settings VS sway

One thing about chrome: I see that you don't include a -flags.conf file for chrome, which afaik means that chrome opens with xwayland. Or did you find another way?

It will be in your default autostart items, I just checked the github of the config files for the Sway edition of Manjaro, here's the link: https://github.com/Manjaro-Sway/desktop-settings/blob/sway/community/sway/etc/sway/config.d/99-autostart-applications.conf .

the command being are are in here.

Really nice! Will try and think about adding this to manjaro sway instead of the pango markup mode lines (e.g. https://github.com/Manjaro-Sway/desktop-settings/blob/sway/community/sway/etc/sway/modes/recording).

added a little configuration example for keyboards into our user skel: https://github.com/Manjaro-Sway/desktop-settings/blob/sway/community/sway/etc/skel/.config/sway/config.d/XX-keyboard.conf.example

Source: https://github.com/Manjaro-Sway/desktop-settings/blob/9b025a7616d399c9e26e28a5e4582062001c3a3a/community/sway/etc/skel/.config/sway/config.d/00-user.conf

Original file: https://github.com/Manjaro-Sway/desktop-settings/blob/sway/community/sway/etc/sway/definitions

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.

I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.

https://github.com/swaywm/sway/issues/7645

https://bugzilla.mozilla.org/show_bug.cgi?id=1743144

Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.

I'm seeing this: https://github.com/swaywm/sway/wiki/Setting-Environmental-Variables but I haven't figured out how to make GDM do it, and I was wondering if there was a super simple "HEY SWAY READ MY .PROFILE" thing I could do.

So I searched around and found the following bug report where this problem and a possible solution was borough up: https://github.com/swaywm/sway/issues/2966 , which was then immediately closed again.

I've been using Sway since late 2019. I like the workflow of a WM. I honestly find it hard to go back to a DE, I like having a minimalistic desktop.

Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway

From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).