wdisplays
kanshi
Our great sponsors
wdisplays | kanshi | |
---|---|---|
12 | 22 | |
172 | 553 | |
- | - | |
5.0 | 5.9 | |
6 months ago | over 2 years ago | |
C | C | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
wdisplays
-
What do you guys use to manage monitors?
For an arandr replacement, https://github.com/swaywm/sway/wiki/i3-Migration-Guide recommends wdisplays.
- How to connect a Sway session to a projector?
-
How to use projector on sway?
But, Sway also supports a Wayland protocol which allows other applications to configure the displays instead. You can read it here if you want the gritty details. My preferred application to configure Sway's outputs is wdisplays.
-
Tiling WM where adding/removing external monitors is easy.
Sway with wdisplays?
-
Are there Wayland equivalents of xrandr and xinput?
You could have a look at wdisplays. Uses wlroots.
-
Three monitor configuration
I run 3 monitors in a similar config manually configured with negative x values for the left most monitor, it worked ok, but now I use https://github.com/artizirk/wdisplays for an easy life
-
(WIP) Working on a GUI for configuring displays
wdisplays comes to mind.
-
Tell HN: Gnome on Wayland Is Amazing
sway laptop user here (for almost 2 years I think?).
I spent a little while on this, but I migrated from i3, so I just ported every little section of my config bit by bit.
In terms of battery bar and other "bar" type things, I use waybar[0] which basically does all the things you'd expect by default (just install and it "works").
For multi-monitor, config, I initially setup with wdisplays[1] (think arandr for wayland) and then manually copied the positions into my sway config. Monitor positioning was the only thing I needed to setup (and telling it that one monitor was HDPI) and then all of the scaling and everything worked perfectly. This was my biggest selling point for wayland, I now get nice crisp fonts and application scaling works nicely (which was not the case with X).
volume control from the keyboard took no time, just a couple of extra lines.
There was some stuff to do with the clipboard (wl-clipboard[2]) and screenshots (grim[3] + slurp[4]) that required some setup, but again, just a few lines, and didn't take much mental load.
Oh and I needed to change my notifications daemon(dunst[5]), and chose to change my program launcher to one with a nicer interface and cleaner fonts (wofi[6]).
I think that's all the tweaking that I did. Oh, and I needed to do something with pipewire to sort out screensharing at the start, don't remember that too well though...
[0] https://github.com/Alexays/Waybar
[1] https://github.com/artizirk/wdisplays
[2] https://github.com/bugaevc/wl-clipboard
[3] https://github.com/emersion/grim
[4] https://github.com/emersion/slurp
[5] https://github.com/dunst-project/dunst
[6] https://hg.sr.ht/~scoopta/wofi
- Arch users belike
-
Setting resolution on Wayland
Try wdisplays.
kanshi
-
Sway external display
Without digging into you problem, i just let you know one options/tool as an addition: https://github.com/emersion/kanshi
-
Starting kanshi from sway
This works, but after a reload of the config the configuration is gone. Then I found this discussion and changed the line to:
-
Arch users belike
Kanshi is not exactly what you're looking for but i stumbled across this when I was writing the dynamic display configuration page.
-
Terminal font size on hidpi + normal display
You should use different scale factors on each monitor. You can do it in your sway configuration, or use something like kanshi that automatically applies different settings based on what is connected.
-
Inaccessible workspaces
If this fixes your problem you'll want to apply this fix: Disable Laptop screen upon closing screen. or you can use something like Automatic display profile switcher when you connect your external display to switch it to while also disabling your laptop screen.
-
How to toggle transparency and gaps? Preserve display configuration?
I also heard of kanshi for monitor configuration, but I believe there's an open bug where sway reload breaks kanshi config... which kind of defeats the purpose.
- Single Background / Multiple Monitors
-
Script for docked mode
kanshi should be able to do it.
-
Organising workspaces on multiple monitors
Assuming your connected monitors may change - you plug another one in and then you want to move workspaces the new output: kanshi can help you with that. You can tell kanshi to execute commands when it matches a profile.
-
Sway not picking the highest refresh rate available
For this you can use kanshi.
What are some alternatives?
wdisplays - GUI display configurator for wlroots compositors
wlr-randr - An xrandr clone for wlroots compositors
sway - i3-compatible Wayland compositor
wayvnc - A VNC server for wlroots based Wayland compositors
linux-tkg - linux-tkg custom kernels
dwl - dwm for Wayland - ARCHIVE: development has moved to Codeberg
grim - Grab images from a Wayland compositor
wl-mirror - a simple Wayland output mirror client
wayland - Core Wayland protocol and libraries (mirror)
Electron - :electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS
wdisplays