Sway customization guide - Revision history

John3-16: Applying section title "Sway - Full-Sized Views, Navigating Using Alt+Tab" approved by patroller on 13.10.2025 in Talk:Sway. Moved introductory passage specific to this configuration option into this section.

2025-10-16T18:04:44Z

Applying section title "Sway - Full-Sized Views, Navigating Using Alt+Tab" approved by patroller on 13.10.2025 in Talk:Sway. Moved introductory passage specific to this configuration option into this section.

← Older revision		Revision as of 18:04, 16 October 2025
Line 1:		Line 1:
	This page documents various customization options available for [[Sway]] that may be of benefit for both desktop/non-technical and technical use. Install [[Sway]] and copy the [[Sway#Sway config file\|Sway config file]] before you proceed.		This page documents various customization options available for [[Sway]] that may be of benefit for both desktop/non-technical and technical use. Install [[Sway]] and copy the [[Sway#Sway config file\|Sway config file]] before you proceed.

			== Sway - Full-Sized Views, Navigating Using Alt+Tab ==
	To set up an environment that launches applications full-sized and to {{Key\|Alt}}+{{Key\|Tab}} between these much as in [[Xfce\|XFCE]] or in various other desktop environments, then a quick setup of the {{Path\|config}} file could effect this. ''Step 4'' is indicated to be sidestepped by those electing an {{Pkg\|i3}}-style, tiled default layout.		To set up an environment that launches applications full-sized and to {{Key\|Alt}}+{{Key\|Tab}} between these much as in [[Xfce\|XFCE]] or in various other desktop environments, then a quick setup of the {{Path\|config}} file could effect this. ''Step 4'' is indicated to be sidestepped by those electing an {{Pkg\|i3}}-style, tiled default layout.

	A launchbar is not set up "out of the box", nor here, so this section only reviews essential ''keybindings'' (or "shortcuts"), saving first-time users from immediately requiring to digest a longer ''"cheatsheet"'' of keybindings that might include resizing, moving and swapping windows (called ''"views"''), say, from smaller tiles (called ''"containers"'') into larger tiles; these may be learned at a later stage.		A launchbar is not set up "out of the box", nor here, so this section only reviews essential ''keybindings'' (or "shortcuts"), saving first-time users from immediately requiring to digest a longer ''"cheatsheet"'' of keybindings that might include resizing, moving and swapping windows (called ''"views"''), say, from smaller tiles (called ''"containers"'') into larger tiles; these may be learned at a later stage.

	~~== Quickstart - config file ==~~

	The quickstart configuration of the {{Path\|config}} file ''may be prepared within or without '''Sway''''' e.g. within an '''Xorg''' session or another compositor, or on another installation, before eventually copying over the finished {{Path\|config}} file onto the target system – except:		The quickstart configuration of the {{Path\|config}} file ''may be prepared within or without '''Sway''''' e.g. within an '''Xorg''' session or another compositor, or on another installation, before eventually copying over the finished {{Path\|config}} file onto the target system – except:

Prabuanand: added back the previous section heading with corrected heading level

2025-10-15T04:23:30Z

added back the previous section heading with corrected heading level

← Older revision		Revision as of 04:23, 15 October 2025
Line 4:		Line 4:

	A launchbar is not set up "out of the box", nor here, so this section only reviews essential ''keybindings'' (or "shortcuts"), saving first-time users from immediately requiring to digest a longer ''"cheatsheet"'' of keybindings that might include resizing, moving and swapping windows (called ''"views"''), say, from smaller tiles (called ''"containers"'') into larger tiles; these may be learned at a later stage.		A launchbar is not set up "out of the box", nor here, so this section only reviews essential ''keybindings'' (or "shortcuts"), saving first-time users from immediately requiring to digest a longer ''"cheatsheet"'' of keybindings that might include resizing, moving and swapping windows (called ''"views"''), say, from smaller tiles (called ''"containers"'') into larger tiles; these may be learned at a later stage.

			== Quickstart - config file ==

	The quickstart configuration of the {{Path\|config}} file ''may be prepared within or without '''Sway''''' e.g. within an '''Xorg''' session or another compositor, or on another installation, before eventually copying over the finished {{Path\|config}} file onto the target system – except:		The quickstart configuration of the {{Path\|config}} file ''may be prepared within or without '''Sway''''' e.g. within an '''Xorg''' session or another compositor, or on another installation, before eventually copying over the finished {{Path\|config}} file onto the target system – except:
	* If one prefers alternative applications to those proposed initially in ''Step 6'' for assignment into specific workspaces. Any such modifications (to be executed in ''Step 7'') could be performed: (a) simply during one's first '''Sway''' session; or (b) by determining what those applications' {{ic\|app_id}} / {{ic\|class}} are (as detailed in ''Step 7''), possibly in another '''Wayland''' session or externally e.g. from documentation.		* If one prefers alternative applications to those proposed initially in ''Step 6'' for assignment into specific workspaces. Any such modifications (to be executed in ''Step 7'') could be performed: (a) simply during one's first '''Sway''' session; or (b) by determining what those applications' {{ic\|app_id}} / {{ic\|class}} are (as detailed in ''Step 7''), possibly in another '''Wayland''' session or externally e.g. from documentation.
	* One will likewise require to verify at some point whether one's chosen applications are installed on the target system; and to install those missing (last step, ''Step 12'').		* One will likewise require to verify at some point whether one's chosen applications are installed on the target system; and to install those missing (last step, ''Step 12'').


	'''''Step 1:'' Assign the main modifier key'''. In a text editor, open the {{Path\|/home/<var>username</var>/.config/sway/config}} file that had been copied over. We will declare what would be the main modifier key for many of our keybindings: {{Key\|Window}}, {{Key\|Alt}} or otherwise. The {{Path\|config}} file has already set the main modifier, called the {{ic\|$mod}} key, to default as the {{ic\|Mod4}} key, also known as the {{Key\|Window}}, {{ic\|Super}} or ''Logo'' key. Verify this towards the beginning of the file:		'''''Step 1:'' Assign the main modifier key'''. In a text editor, open the {{Path\|/home/<var>username</var>/.config/sway/config}} file that had been copied over. We will declare what would be the main modifier key for many of our keybindings: {{Key\|Window}}, {{Key\|Alt}} or otherwise. The {{Path\|config}} file has already set the main modifier, called the {{ic\|$mod}} key, to default as the {{ic\|Mod4}} key, also known as the {{Key\|Window}}, {{ic\|Super}} or ''Logo'' key. Verify this towards the beginning of the file:

Prabuanand: moved the Sway#Quickstart - config File to it's own page as per Talk:Sway#Sway#Quickstart_-_config_File

2025-10-15T04:10:32Z

moved the Sway#Quickstart - config File to it's own page as per Talk:Sway#Sway#Quickstart_-_config_File

New page

This page documents various customization options available for [[Sway]] that may be of benefit for both desktop/non-technical and technical use. Install [[Sway]] and copy the [[Sway#Sway config file|Sway config file]] before you proceed.

To set up an environment that launches applications full-sized and to {{Key|Alt}}+{{Key|Tab}} between these much as in [[Xfce|XFCE]] or in various other desktop environments, then a quick setup of the {{Path|config}} file could effect this. ''Step 4'' is indicated to be sidestepped by those electing an {{Pkg|i3}}-style, tiled default layout.

A launchbar is not set up "out of the box", nor here, so this section only reviews essential ''keybindings'' (or "shortcuts"), saving first-time users from immediately requiring to digest a longer ''"cheatsheet"'' of keybindings that might include resizing, moving and swapping windows (called ''"views"''), say, from smaller tiles (called ''"containers"'') into larger tiles; these may be learned at a later stage.

The quickstart configuration of the {{Path|config}} file ''may be prepared within or without '''Sway''''' e.g. within an '''Xorg''' session or another compositor, or on another installation, before eventually copying over the finished {{Path|config}} file onto the target system – except:
* If one prefers alternative applications to those proposed initially in ''Step 6'' for assignment into specific workspaces. Any such modifications (to be executed in ''Step 7'') could be performed: (a) simply during one's first '''Sway''' session; or (b) by determining what those applications' {{ic|app_id}} / {{ic|class}} are (as detailed in ''Step 7''), possibly in another '''Wayland''' session or externally e.g. from documentation.
* One will likewise require to verify at some point whether one's chosen applications are installed on the target system; and to install those missing (last step, ''Step 12'').

'''''Step 1:'' Assign the main modifier key'''. In a text editor, open the {{Path|/home/<var>username</var>/.config/sway/config}} file that had been copied over. We will declare what would be the main modifier key for many of our keybindings: {{Key|Window}}, {{Key|Alt}} or otherwise. The {{Path|config}} file has already set the main modifier, called the {{ic|$mod}} key, to default as the {{ic|Mod4}} key, also known as the {{Key|Window}}, {{ic|Super}} or ''Logo'' key. Verify this towards the beginning of the file:

<Pre>
# Logo key. Use Mod1 for Alt.
set $mod Mod4
</Pre>

As proposed there, one could change that {{ic|$mod}} key to be the {{Key|Alt}} key a.k.a. the {{ic|Mod1}} key. To change the {{ic|$mod}} key assignment, as with any line in this file, one could edit/delete the lines or comment such line out i.e. add a hashtag ('''''#''''') at the start of any line that does not begin with a hashtag, so that such line would not be executed by '''Sway''' but would be left there for reference; and then enter the customised version of that line below it. Note that '''Sway''' [https://github.com/swaywm/sway/wiki#comments does not support] comments at the end of an executable line, following a hashtag.

According to the {{ic|man 5 sway}} page, ''XKB modifier names'' can be used to refer to modifier keys, plus certain aliases found among the following list, all of these "{{ic|codes}}" being acceptable for use throughout the configuration file:

* {{ic|Mod1}} - {{Key|Alt}} - Alternatively expressed as {{ic|Alt}};
* {{ic|Mod2}} - Although not universally mapped, here it refers to the {{Key|Num Lock}} key;
* {{ic|Mod3}} - It could be programmed, as an XKB modifier key;
* {{ic|Mod4}} - Alternatively expressed as the {{ic|Super}} key, a.k.a. the {{Key|Window}} or ''Logo'' key;
* {{ic|Mod5}} - {{Key|AltGr}};
* {{ic|Lock}} - {{Key|Caps Lock}};
* {{ic|Control}} - {{Key|Ctrl}} - Alternatively expressed as {{ic|Ctrl}}; and
* {{ic|Shift}} - {{Key|Shift}}.

It might be best not to use the {{Key|Ctrl}} key as the ''main modifier'', as it is often used in applications e.g. {{Key|Control}}+{{Key|c}} to ''copy'', {{Key|Control}}+{{Key|b}} for ''bold'', etc. Similarly when considering the {{ic|Shift}} as main modifier.

So, if one were to choose, say, the {{Key|Alt}} key as the main modifier, that {{ic|Mod4}} line could be changed to: {{ic|set $mod Alt}} or {{ic|set $mod Mod1}}. We will preserve the default, {{ic|Mod4}} ({{Key|Window}}), as the main modifier. Note that any modification will not be manifested until one chooses at any time to reload the {{Path|config}} file by hitting {{ic|$mod+Shift+c}} (cf. ''Step 10'').

'''''Step 2:'' Declare what your default terminal and menu launcher will be'''. In this {{Path|config}} file, these are currently configured to be the {{Pkg|foot}} terminal; and {{Pkg|wmenu}}, which supplies the {{ic|wmenu-run}} command:

<Pre>
# Your preferred terminal emulator
set $term foot
# Your preferred application launcher
set $menu wmenu-run
</Pre>

You could leave these 'as is' if you are happy with these selections. Otherwise, substitute any of them.

A word to the wise regarding one's initial choice of ''terminal'' ''if not currently running '''Sway''''': if a different terminal were to be chosen, then one would not be able to {{Key|Alt}}+{{Key|Tab}} back and forth from a launched '''foot''' terminal into other opened workspaces unless that terminal's {{ic|app_id}} / {{ic|class}} could somehow be determined and specified by the user in ''Step 7''. It may be more suitable therefore to leave '''foot''' as the default terminal until one of these could be determined once a '''Sway''' session is run, so that the terminal ('''foot''') would land in a specified workspace when launched, and then easily {{Key|Alt}}+{{Key|Tab}} to and from it. Alternatively, one could left-click on the chosen terminal's workspace button on the top {{Pkg|swaybar}} in order to switch to that workspace. (Note also that '''foot''' would already be installed if '''Sway''' had been installed using {{ic|$ doas setup-desktop sway}}). On the other hand, ''if one is currently running '''Sway''''', then it is straightforward to change this default terminal choice here, if so wished; a tweak for the preferred terminal could be made in ''Step 7''.

One's choice of menu launcher here is more flexible, regardless of the compositor/window manager currently being used, as the launcher will appear in any workspace currently displayed on-screen – a.k.a. the workspace ''in focus'' – using the keybinding declared in the following step (''Step 3''). Insert the preferred launcher's launch command here. For example, one may prefer {{Pkg|rofi}} over '''wmenu'''; Alpine Linux's '''rofi''' port now supports '''Wayland''', just as [https://github.com/davatorium/rofi rofi's mainline version] officially has since 2025. If so, that {{ic|set $menu wmenu-run}} line could be changed as follows:

<Pre>
set $menu '/usr/bin/rofi -combi-modi run,drun,window,filebrowser -show combi -sort'
</Pre>

With that menu instruction, whenever '''rofi''' is launched using the keybinding reviewed in the next step, it would first offer a ''combi'' (combination) menu of all packages and of <code>.desktop</code> files that match the the command name while it is being typed in; alternatively, one could follows this on by hitting {{Key|Control}}+{{Key|Tab}}, which in turn would offer (a) a ''drun'' menu (a launcher strictly of <code>.desktop</code> files); (b) a listing of opened ''"window"''/view selections; or (c) a simple ''filebrowser'', etc.

A tally of the chosen packages is being kept for any required installation later.

'''''Step 3:'' Choose key combinations to open the terminal and launcher and others'''. From the configuration file:

<Pre>
bindsym $mod+Return exec $term
[...]
bindsym $mod+d exec $menu
</Pre>

Modify these keybindings if so wished, which refer to the terminal and application launcher chosen in ''Step 2''. Ensure that any different chosen key combination(s) has/have not already been assigned elsewhere in this {{Path|config}} file. Make note of your chosen terminal and menu keybindings so as to know how to launch them later. As it stands:
* {{Key|Window}}+{{Key|Return}} for your terminal;
* {{Key|Window}}+{{Key|m}} for your menu launcher;
Substitute the {{Key|Window}} key for your assigned {{ic|$mod}} key, or with any other chosen combination that has not been used elsewhere in the configuration file.

Keybindings may also be made without requiring to define applications as variables that use the {{ic|set}} instruction and the {{ic|$}} variable prefix. For example, having ensured that there was no previous binding for {{ic|Control+Alt+w}}, one could add the following keybinding:

<Pre>
# LibreOffice Writer shortcut
bindsym Control+Alt+w exec '/usr/bin/libreoffice --writer'
</Pre>

'''''Step 4:'' Applications to launch full-sized and in tabbed layout (Optional)'''. At the beginning of the {{ic|# Layout stuff:}} section, Consider inserting:

<Pre>
workspace_layout tabbed
</Pre>

Then, each launched application will launch full-sized. Each application will be named in a tab.
If opting for a default tiled layout, this step is omitted. Tiling sends applications by default into tiles/"containers", splitting the screen, unless assigned to different workspaces in ''Steps 6-7''. A further alternative would be: {{ic|workspace_layout stacking}}.

'''''Step 5:'' Focus when launched (Optional)'''. Make '''Sway''' to immediately focus on any newly-opened application. At the end of the {{ic|# Workspaces:}} section in this {{Path|config}} file, consider adding:

<Pre>
for_window [app_id=.*] focus
</Pre>

This may be suitable to avoid having to navigate to its tab/workspace. It also ensures that dialog boxes such as ''"Open ..."'' and ''"Save as..."'' appear in the currently focused workspace.

'''''Step 6:'' Assign workspaces'''. This is proposed for your most oftenly-used applications, so that most applications will land into different workspaces, and then one could {{Key|Alt}}+{{Key|Tab}} between those applications/workspaces.

Consider copying and pasting the following model in this same {{ic|# Workspaces:}} passage. Customise each line for user preferences. These specify the {{ic|app_id}} for various applications, including that of the {{Pkg|keepassxc}} password vault, the lean {{Pkg|corepad}} text editor and {{Pkg|okular}} pdf viewer. Then, one finishes off each line with a chosen workspace number. (There may be no documented upper limit of workspaces, but one would need two keystrokes to move applications into two-digit workspaces if and when such keybindings were eventually learned and used.)

<Pre>
# APPLICATIONS TO APPEAR IN SPECIFIC WORKSPACES
assign [app_id="foot"] 1
assign [app_id="chromium"] 2
assign [app_id="org.keepassxc.KeePassXC"] 3
assign [app_id="cc.cubocore.CorePad"] 4
assign [app_id="libreoffice-writer"] 5
assign [app_id="libreoffice-calc"] 6
assign [app_id="org.kde.okular"] 7
assign [app_id="thunar"] 8
</Pre>

One could use workspace names instead of numbers, but then one would need to change their instances in the default {{Path|config}} file. Some applications, not listed here, may require identification by their {{ic|class}} name instead of by {{ic|app_id}} – particularly, some that were originally designed for '''X11''' (such as '''xterm''') – see ''Step 6''. '''Sway''' supplies the {{ic|swaymsg}} command that could determine the {{ic|app_id}} and/or {{ic|class}} name of one's chosen applications.

{{Tip|The '''keepassxc''' password vault is assigned to appear in a different workspace than the '''chromium''' browser. After both are launched, then one would be able to {{Key|Alt}}+{{Key|Tab}} between the two workspaces to fetch/paste password data without engaging a browser password extension, if preferred.}}

If alternative applications are to be assigned workspaces, proceed to the next step.

'''''Step 7:'' Assign alternative application choices for specific workspaces (Optional)'''. This may require being run in a '''Sway''' session. ''If not currently running Sway'', then consider conserving whichever part of the code block in ''Step 6'' that is applicable for user purposes in the configuration file and resuming this ''Step 7'' once the first '''Sway''' session is run.

This step may succeed alternatively in a different '''Wayland''' compositor provided that: (a) '''Sway''' or {{Pkg|sway-bash-completion}} has been installed, seeing how either supply the required {{ic|swaymsg}} command; or (b) one has a different means of determining the {{ic|app_id}} / {{ic|class}} of the alternative application(s).
<ol start="1">
<li> Launch the alternative applications that are to be assigned to workspaces.</li>
<li> Run {{ic|<nowiki>swaymsg -t get_tree | grep "app_id"</nowiki>}} in a terminal. The command examines metadata for your opened windows, and the result is then whittled down (or ''"grepped"'') to display {{ic|app_id}} values. For example: </li>
<pre> $ swaymsg -t get_tree | grep "app_id"
"app_id": "Alacritty",
"app_id": "firefox-esr",
"app_id": "librewolf",
"app_id": "pavucontrol-qt",
"app_id": "featherpad",
"app_id": "audacious",
"app_id": "org.gnome.Epiphany",
"app_id": "org.qutebrowser.qutebrowser",
</pre></ol>
<ol start="3">
<li> Plug the {{ic|app_id}} values for any preferred applications into the {{ic|assign}} listings code block above; end each line with a chosen workspace number.</li>
<li> In case any application name did not appear with an {{ic|app_id}}, then it is possible that the application was originally designed for '''Xorg''' and has not been fully adapted for ''"pure '''Wayland'''"'': for example, {{Pkg|xterm}}. In that case, one would need to determine what its {{ic|class}} is instead: ''with {{Pkg|xwayland}} installed and not disabled'' in '''Sway''', launch '''xterm'''; then, in a terminal, run:</li>
<pre>
$ swaymsg -t get_tree | grep "class"
"class": "XTerm",
</pre>
<li>Determine the {{ic|class}} values for the remainder of the preferred applications that required {{ic|class}} identifiers instead of {{ic|app_id}} and create lines for them in the {{ic|assign}} code block above. For instance, for '''xterm''' to land in workspace 9, add a line to specify its ''class'' and its assigned workspace ''number'':
<pre>
assign [class="XTerm"] 9
</pre><li>
</ol>

'''''Step 8:'' Navigating between applications in different workspaces'''. Tell '''Sway''' what will be the chosen way to ''tab back'' through the workspaces that contain launched applications on a single monitor, say, {{Key|Alt}}+{{Key|Tab}}. In the {{ic|# Moving around:}} passage, consider adding:-

<Pre>
bindsym Alt+Tab workspace prev_on_output
bindsym Super+Tab workspace next_on_output
</Pre>

We have additionally assigned {{Key|Super}}+{{Key|Tab}} to tab ''forwards'' through workspaces, in case that this could be useful to the user (optional).

As mentioned, one can alternatively focus a different workspace by left-clicking on its worskpace button in the '''swaybar'''.

'''''Step 9:'' Navigating between applications within the same workspace'''. If two or more instances of the same application get launched (say, two instances of '''foot'''), then they will both appear in the same workspace that had been assigned to them, if any. In such case, {{Key|Alt}}+{{Key|Tab}} would not work to navigate between these because that keybinding navigates between applications being displayed in ''different'' workspaces. Instead, one may navigate between those two instances/tabs within that same workspace in ''three alternative ways''; no edits need be done, but one may need to make note of these methods:-

* The default {{Path|config}} file has already bound {{ic|$mod+Left}} and {{ic|$mod+Right}} to switch focus onto tabs shown to the left and right within the same workspace; in our setup, that would be {{Key|Window}}+{{Key|←}} and {{Key|Window}}+{{Key|→}}.
* The default {{Path|config}} file has similarly bound {{ic|$mod+$left}} and {{ic|$mod+$right}} for these same commands; the {{ic|$left}} and {{ic|$right}} ''"key variables"'', along with two others, have been defined in a fashion that would be familiar to those using {{Pkg|vim}}:

<pre>
set $left h
set $down j
set $up k
set $right l </pre>

:Although the {{ic|Left}} key ({{Key|←}}) is distinct from the {{ic|$left}} key (assigned here to be the {{Key|h}} key), this {{Path|config}} file has ''bound them both'' to enact the same action when combined with the {{ic|$mod}} key, specifically, to move ''left'' through tabs in the same workspace (different users prefer alternative methods):

<pre>
bindsym $mod+$left focus left
[...]
bindsym $mod+Left focus left </pre>

:Similarly for the {{ic|$right}} and {{ic|Right}} keys.

* Alternatively, one could ''left-click'' on a tab to focus on a specific application instance, similarly to how one might click on ''taskbar'' items in other desktop environments.

Any applications that were not assigned into a workspace in the {{ic|assign}} ''Steps 6-7'' above will also launch into the workspace currently focused. In such cases, therefore, their tabs would be created in the current workspace too, and one could navigate between such applications, within that same workspace, using any way reviewed in this step also.

'''''Step 10:'' Floating, dragging, tiling, fullscreen, etc'''.
* One may make a focused application to '''float''', and to toggle ''"floating"'' off as-and-when needed, with: {{ic|$mod+Shift+space}} . In our setup: {{Key|Window}}+{{Key|Shift}}+{{Key|Space}}.

* The {{Path|config}} file points out that one may ''"drag floating windows by holding down $mod and left mouse button"''. Seeing how {{ic|$mod}} was kept assigned as the {{Key|Window}} key: {{Key|Window}}+'''drag'''. The window needs to be floating first; in some instances, one may need to drag at the tab.

* One could make some applications to launch "floating" by default (optional). An application that is sometimes made to float by default is the {{Pkg|galculator}} calculator pad; just add:
:{{ic|<nowiki>for_window [app_id="galculator"] floating enable</nowiki>}}

* To toggle through '''tiled layouts''' within a workspace: {{ic|$mod+e}} / {{Key|Window}}+{{Key|e}}

* To return to '''full-sized tabs''' i.e. window-sized after being in a tiled layout, yet not fullscreen, thereby retaining toolbars, etc: {{ic|$mod+w}} / {{Key|Window}}+{{Key|w}} . Floating windows and fullscreen windows need to be toggled off first.

* To toggle in and out of '''fullscreen''': {{ic|$mod+f}} / {{Key|Window}}+{{Key|f}}

Take note of two final keybindings, or modify these first:

* To '''reload''' the '''Sway''' configuration file after editing it during a session: {{ic|$mod+Shift+c}} / {{Key|Window}}+{{Key|Shift}}+{{Key|c}}

* To '''exit''' '''Sway''' and the login session (save your work first): {{ic|$mod+Shift+e}} / {{Key|Window}}+{{Key|Shift}}+{{Key|e}}

'''''Step 11:'' Add variables and autostart instructions'''. These could be added to the beginning of this {{Path|config}} file. Typically, various environment variables would require being set before launching a '''Wayland''' compositor, for example, in {{Path|~/.profile}} . Do not add ampersands ('''&''') at the end of each line in {{Path|config}}, unlike with {{Path|.xinitrc}} syntax in '''Xorg'''.

{{Pkg|xwayland}}, if not required, can be disabled by inserting a line here to that effect. Alternatively, omit that line or comment it out by using a hashtag, as in the following example of autostart instructions, where '''Sway''' is assumed to have been launched [[Sway#Starting_Sway|using a {{ic|dbus-run-session}}]]; gui runlevel is started now if '''PipeWire''' and associated services are being [[PipeWire#Pipewire_user_service|launched as user services]]; and where '''chromium''' is also autostarted:

<Pre>
exec dbus-update-activation-environment WAYLAND_DISPLAY DISPLAY XDG_CURRENT_DESKTOP=sway SWAYSOCK I3SOCK XCURSOR_SIZE XCURSOR_THEME
# xwayland disable
# Start gui runlevel for PipeWire and associated services to launch now
exec openrc -U gui
exec /usr/bin/chromium
</Pre>

{{Tip|Running ''"pure '''Wayland'''"'' – i.e. without the '''xwayland''' layer/package – may remove a possible attack surface. '''Xwayland''' could be required, however, to run certain '''Xorg'''-designed software, such as {{Pkg|xterm}}. One may also investigate '''libreoffice''' and '''okular''' functionality.}}

'''''Step 12:'' Install selected packages'''. Ensure that all mentioned applications have been installed: {{ic|apk info -e <var>package1</var> <var>package2</var>}}. Substitute entries in the following list with one's packages mentioned in the {{Path|config}} file:

{{Cmd|$ apk info -e foot wmenu chromium keepassxc corepad libreoffice okular thunar xterm galculator}}

'''wmenu''' was preserved for that listing; swap it out for '''rofi''' or otherwise, if necessary. One may have decided also not to include '''xterm''', etc.

Install any application not appearing in the output of that instruction.

== See also ==
* [[Sway]]

[[Category:Compositor]]