Skip to main content
Version: 2.2 (dev)

Try SomeWM without logging out somewm-only

Run SomeWM in a window, open a terminal inside it, and stop the nested session. You need SomeWM 2.1 and somewm-client on your PATH, a graphical session, and a terminal emulator such as Alacritty.

The nested compositor has its own windows and configuration. It still runs as your user and shares your files and services, so it is not a sandbox.

Start a nested instance​

From a terminal in a Wayland session, run:

somewm-client test start

On an X11 desktop, use somewm-client test start --host x11 instead.

A window titled somewm:test:test opens. Without --config, it uses the normal config search path, including your existing user config. The steps below assume the shipped default. The command prints the instance's PID, socket and log paths, and shortcut handling. Read its keybinds: line. If the host cannot forward Super shortcuts, the nested session remaps Mod4 to Mod1 (Alt).

Open a terminal​

Run this from your outer terminal, substituting a terminal you have installed:

somewm-client test run -- alacritty

Click inside the nested window, then press Mod4+Return, or Alt+Return if remapped. The default config starts foot, so install it if you want that shortcut to open a second terminal.

Press Mod4+Space to change the layout. The default starts tiled. The next layout puts the master area on the right.

Try a configuration change​

Make a separate copy of your rc.lua, for example ~/somewm-test/rc.lua. If you do not have one, copy the shipped default using the paths in First Launch.

Stop the default instance and start one with your copy:

somewm-client test stop
somewm-client test start --config ~/somewm-test/rc.lua

Add --host x11 to the start command on X11. In the copied file, change local terminal = "foot" to an installed terminal, save, then run:

somewm-client test reload

Press the terminal shortcut inside the nested window. It should launch your chosen terminal. If loading fails, inspect the log with somewm-client test logs.

Stop the instance​

somewm-client test stop

The nested window closes and its state directory and log are removed. Copy the log first if you need it for troubleshooting.

Continue with Basics, or use the nested testing guide for named instances, headless tests, and command-line inspection.