You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add Print for screenshot use-case (grim -g "`slurp`")
Add XF86PowerOff for logout manager use-case (wlogout?)
how to adjust "dynamic" env vars like PATH, e.g.
inherit environment, so setting it before starting labwc
having it in .bashrc might require using bash -i -c in the keybind, at least on some distros (Debian when not restarting labwc after changes to .bashrc)
having it in .profile might require using sh -l in the keybind, depending on how labwc was started
if the env var is already set when starting labwc the -l argument is not required because labwc (and thus the Execute action) inherits its startup environment
..
The Execute action doesn't use a shell, how to use && and similar things in a keybind
easiest solution: external script which then gets called via the keybind
prefixing the command by sh -c like sh -c "command 1; command 2;"
due to the XML nature of the config file, some characters have to be escaped, like & -> & or > -> >
Tips / Tricksand / orGetting started, Keyboard Layout:man 7 xkeyboard-configXKB_DEFAULT_LAYOUTFAQPrintfor screenshot use-case (grim -g "`slurp`")XF86PowerOfffor logout manager use-case (wlogout?)PATH, e.g..bashrcmight require usingbash -i -cin the keybind, at least on some distros (Debian when not restarting labwc after changes to.bashrc).profilemight require usingsh -lin the keybind, depending on how labwc was started-largument is not required because labwc (and thus theExecuteaction) inherits its startup environmentExecuteaction doesn't use a shell, how to use&&and similar things in a keybindsh -clikesh -c "command 1; command 2;"&->&or>->>*window rule withserverDecoration="no"Meta: