BONK
January 19, 2021, 6:29pm
122
Display configuration
Sway manages displays for you, xrandr should not be used.
Run swaymsg -t get_outputs to get a list of output names. Then use the output command to arrange your displays.
For detailed information, check the manual. Run man 5 sway-output.
Multihead
Managing multiple monitors is simple through the use of multiple output commands.
e.g., if we want to have a monitor with HDMI1 and a resolution of 1920x1080, and to the right of it a laptop monitor with eDP1 and a resolution of 1600x900; the following two commands can be placed in your config file:
output HDMI1 pos 0 0 res 1920x1080
output eDP1 pos 1920 0 res 1600x900
Take a note that you might want to change the focus of monitor on sway launch. Add this to your sway config:
focus output <name-or-identifier>
or
exec swaymsg focus output <name-or-identifier>
so it doesn’t trigger on reload.
For more details read man 5 sway-output.
1 Like
I will add this to the config
I have an issue: When I try to kill a window with mod+shift+c it kills waybar instead. Anyone have the same experience?
Also, shoudn’t we go with Arc-Dark instead of Arc?
Kill a window is just $mod+c
It is pretty non-dark at me. Both the file manager and firefox
1 Like
BONK
January 19, 2021, 6:48pm
129
morten-b:
file manager
Did you use a file manager that has root access?
Its fixed now. The was an error in sway config. For both filemanager and firefox
2 Likes
Sorry!! Can you also delete autostart? We don’t need it anymore.
I’ve added a mode to shutdown, logout etc. It is activated with mod+e.
The text of waybar is not very nice when this is activated, but it is functional.
Is the shutdown button of waybar able to mimic a keyboard combo? So that we can activate the sway mode from there?
Yes it is. Instead of wlogout in waybar config under “custom/power on-click” launch your sway mode instead.
Yeah, but launching is done with a key combo, not like execiting a script. And ydotool, which could have been used for this is only in AUR
Could you turn that mode into a script??
Hmmmm… I really don’t have any idea.
seems it do not take gtk theme at all and uses the defaults, i do put this what will read the theme settings from the files and apply it:
added this to config file:
# apply gtk theming
exec_always ~/.config/sway/scripts/import-gsettings
~/.config/sway/scripts/import-gsettings:
#!/bin/sh
# usage: import-gsettings
config="${XDG_CONFIG_HOME:-$HOME/.config}/gtk-3.0/settings.ini"
if [ ! -f "$config" ]; then exit 1; fi
gnome_schema="org.gnome.desktop.interface"
gtk_theme="$(grep 'gtk-theme-name' "$config" | cut -d'=' -f2)"
icon_theme="$(grep 'gtk-icon-theme-name' "$config" | cut -d'=' -f2)"
cursor_theme="$(grep 'gtk-cursor-theme-name' "$config" | cut -d'=' -f2)"
font_name="$(grep 'gtk-font-name' "$config" | cut -d'=' -f2)"
gsettings set "$gnome_schema" gtk-theme "$gtk_theme"
gsettings set "$gnome_schema" icon-theme "$icon_theme"
gsettings set "$gnome_schema" cursor-theme "$cursor_theme"
gsettings set "$gnome_schema" font-name "$font_name"
2 Likes
You put my stuff in a script? Clever. Are you adding to your fork? Or a pull request?
Thank you!!
