mirror of
https://github.com/swaywm/sway.git
synced 2026-04-28 06:46:26 -04:00
f1d64f811d
When running Sway from a display manager, a user's login shell is not used. Because of this, profile scripts are not run and the environment may not be configured. As suggested in #3109, this can be solved by a wrapper that runs sway via the user's configured shell. This is similar to the approach taken by GNOME to source the standard set of profile scripts. This could be accomplished with a shell script, but a dedicated binary avoids dependencies on specific shells. The sway.desktop wayland session file is also updated to call the swayrun wrapper.
34 lines
749 B
Markdown
34 lines
749 B
Markdown
swayrun(1)
|
|
|
|
# NAME
|
|
|
|
swayrun - Run Sway from a login shell
|
|
|
|
# SYNOPSIS
|
|
|
|
_swayrun_ [options...] [command]
|
|
|
|
# DESCRIPTION
|
|
|
|
Attempts to run *sway*(1) via the user's login shell. This allows environment
|
|
configuration and other login actions, for example when run via a login manager.
|
|
|
|
All arguments to swayrun will be passed through unaltered to sway.
|
|
|
|
If a valid login shell cannot be determined, sway will be executed normally.
|
|
|
|
# CONFIGURATION
|
|
|
|
swayrun will consult */etc/shells* if it exists for a list of valid login
|
|
shells. In addition, *false* and *nologin* will be considered invalid shells.
|
|
|
|
# ENVIRONMENT
|
|
|
|
The following environment variables have an effect on swayrun:
|
|
|
|
_SHELL_
|
|
Holds the path to the login shell.
|
|
|
|
# SEE
|
|
|
|
*sway*(1) *shells*(5)
|