labwc-actions(5)
π labwc-actions(5) π
bestie, this is the File Formats Manual page for labwc-actions(5), and it is literally the action cheat sheet. π
πΈ NAME πΈ
labwc - actions
β¨ ACTIONS β¨
Actions are used in menus and keyboard/mouse bindings. periodt. π«Ά
<action name="Close" />β closes the top-most window. bye bestie π<action name="Kill" />β kills the process associated with the current window by sending it theSIGTERMsignal. dramatic but necessary π<action name="Execute" command="value" />β executescommand. Note that in the interest of backward compatibility, labwc supports<execute>as an alternative to<command>even though openbox documentation states that it is deprecated. Note: tilde (~) is expanded in the command before passing toexecvp(). iconic little detail β¨<action name="Exit" />β exits labwc. closing time πͺ<action name="Focus" />β gives focus to the window under the cursor. π<action name="Unfocus" />β removes focus from the window that is currently focused. release the spotlight bestie π<action name="Raise" />β restacks the current window above other open windows. main character energy π<action name="Lower" />β restacks the current window below other open windows. humble era πΈ<action name="Iconify" />β iconifies (minimizes) the focused window. tiny nap time π΄<action name="Move" />β begins interactive move of the window under the cursor. grab and go π«Ά<action name="MoveToEdge" direction="value" snapWindows="value" />β moves the window until it hits the next edge.direction[left|up|right|down]β direction in which to move.snapWindows[yes|no]β move window until it hits an edge of another window or screen edge. If set to"no", only move to the next screen edge. Default isyes.
<action name="Resize" direction="value" />β begins interactive resize of the window under the cursor.direction[up|down|left|right|up-left|up-right|down-left|down-right]β edge or corner from which to start resizing. If this is not provided, the direction is inferred from the cursor position.
<action name="ResizeRelative" left="" right="" top="" bottom="" />β resizes the window relative to its current size. Values ofleft,right,toporbottomtell how much to resize on that edge of the window; positive values grow the window, negative values shrink the window.
Note that some applications like terminal emulators may refuse growing or shrinking by small amounts to keep the window size aligned to their internal cell size. tiny pixel perfectionist behavior π
<action name="GrowToEdge" direction="value" />β resizes the window to fill the space between its edge and any other window edge.direction[left|up|right|down]β direction in which to grow.
<action name="ShrinkToEdge" direction="value" />β reverse ofGrowToEdge. Shrinks by a maximum of 50%.direction[left|up|right|down]β direction in which to shrink.
<action name="MoveTo" x="" y="" />β moves to position (x,y). coordinates bestie π<action name="ResizeTo" width="" height="" />β resizes the window.widthβ the width to resize the window to in pixels.heightβ the height to resize the window to in pixels.
<action name="MoveToCursor" />β moves to be centered on the cursor. Tries to prevent any part of the window from going off-screen. This action is deprecated from v0.7.3. To ensure your config works in future labwc releases, please use:
<action name="AutoPlace" policy="cursor">
<action name="MoveRelative" x="" y="" />β moves the window relative to its current position. Positive value ofxmoves it right, negative left. Positive value ofymoves it down, negative up. slide to the left, slide to the right πΊ<action name="ToggleSnapToEdge" direction="value" combine="value" />β resizes the window to fill half or quarter the output in the given direction.direction[up|down|left|right|up-left|up-right|down-left|down-right|center]β direction in which to snap the window.combine[yes|no]β allows to snap a window to an output corner by combining two directions. For example, snapping a window torightand then toupplaces it in the up-right quarter of the output. Default isno.
ToggleSnapToEdge additionally toggles the active window between tiled to the given direction and its untiled position. toggling is the moment β¨
<action name="SnapToEdge" direction="value" combine="value" />β resizes the window to fill half or quarter the output in the given direction.direction[up|down|left|right|up-left|up-right|down-left|down-right|center]β direction in which to snap the window.combine[yes|no]β allows to snap a window to an output corner by combining two directions. For example, snapping a window torightand then toupplaces it in the up-right quarter of the output. Default isno.
<action name="ToggleSnapToRegion" region="value" />β resizes and moves the active window according to the given region.
ToggleSnapToRegion additionally toggles the active window between tiled to the given region and its untiled position.
See labwc-config(5) for further information on how to define regions. iykyk π¦
<action name="SnapToRegion" region="value" />β resizes and moves the active window according to the given region.
See labwc-config(5) for further information on how to define regions. π¦
<action name="UnSnap" />β resizes and moves the active window back to its untiled or unmaximized position if it had been maximized or tiled to a direction or region. reverse card, bestie πNextWindow,PreviousWindow,NextWindowImmediate,PreviousWindowImmediateβ cycle focus to next/previous window, respectively. the group chat of window actions π¬
<action name="NextWindow" workspace="current" output="all"
identifier="all" />
<action name="PreviousWindow" workspace="current" output="all"
identifier="all" />
<action name="NextWindowImmediate" workspace="current" output="all"
identifier="all" />
<action name="PreviousWindowImmediate" workspace="current" output="all"
identifier="all" />
- Default keybinds for
NextWindowandPreviousWindowareAlt-TabandShift-Alt-Tab. While cycling through windows, the arrow keys move the selected window forwards/backwards and the escape key halts the cycling. β¬ οΈβ‘οΈ NextWindowImmediateandPreviousWindowImmediateskip the Window Switcher and OSD, useful for binding to keys without modifiers.workspace[all|current]β this determines whether to cycle through windows on all workspaces or the current workspace. Default is"current".output[all|focused|cursor]β this determines whether to cycle through windows on all outputs, the focused output, or the output under the cursor. Default is"all".identifier[all|current]β this determines whether to cycle through all windows or only windows of the same application as the currently focused window. Default is"all".
<action name="Reconfigure" />β re-loads configuration and theme files. refresh era π<action name="ShowMenu" menu="root-menu" />β shows a menu. menu moment fr π
<action name="ShowMenu" menu="MENU">
<atCursor>yes|no</atCursor>
<position>
<x>X</x>
<y>Y</y>
</position>
</action>
menuβ the name of the menu to show. The menus"root-menu","client-menu","client-send-to-menu"and"client-list-combined-menu"are guaranteed to exist, but others may be defined explicitly. Seelabwc-menu(5)for more information.atCursor[yes|no]β when opening a menu, open the menu at the location of the mouse cursor. When set tono, the menu will appear at the upper-left corner of the window associated with the action or underneath the window button that opened the menu. Default isyes.positionβ show the menu in the specified position on the monitor that has cursor focus, see below.
The position tag has two sub-tags. <x> and <y> specify a position and take either a pixel value, the string "center" which will center the menu in that dimension, or a relative value specified as a percentage. A relative value is interpreted in terms of the monitor the menu will be shown on, and will be relative to the left/top edge of the menu window and monitor for positive values, and to the right/bottom edge for negative values.
The example below demonstrates how the root-menu can be opened from a bottom aligned panel using the command wtype -M logo -k Space:
<keybind key="W-Space">
<action name="ShowMenu">
<menu>root-menu</menu>
<position>
<x>0</x>
<y>-0</y>
</position>
</action>
</keybind>
<action name="SetDecorations" decorations="value" forceSSD="no" />β sets decorations of the focused window.decorations[full|border|none]βfullenables the whole server side decorations. Withborder, only the borders and invisible resize area are enabled.nonedisables everything.forceSSD[yes|no]β if this isno, this action will be ignored for windows that have client side decorations if it would increase the amount of decoration. Default isno.
<action name="ToggleDecorations" />β toggles decorations of the focused window.
This is a 3-state action which can be executed multiple times:
- Only the titlebar will be hidden, borders and resize area are kept
- Remaining decorations will be disabled
- Decorations will be shown normally
By disabling the theme configuration keepBorder the first step will be removed and the action only toggles between on and off. three-state slay π
<action name="ToggleFullscreen" />β toggles fullscreen state of the focused window. big screen energy π₯<action name="ToggleMaximize" direction="value" />β toggles maximize state of the focused window. Supported directions are"both"(default),"horizontal", and"vertical".<action name="Maximize" direction="value" />β maximizes the focused window in the direction(s) specified. Supported directions are"both"(default),"horizontal", and"vertical".<action name="UnMaximize" direction="value" />β unmaximizes the focused window in the direction(s) specified and returns it to its pre-maximized dimensions. Supported directions are"both"(default),"horizontal", and"vertical".<action name="ToggleAlwaysOnTop" />β toggles always-on-top of the focused window. stay on top, no cap π<action name="ToggleAlwaysOnBottom" />β toggles between layersalways-on-bottomandnormal. When a window is in thealways-on-bottomlayer, it is rendered below all other top-level windows. It is anticipated that this action will be useful when defining window-rules for desktop-management tools that do not support thewlr-layer-shellprotocol. bottom layer bestie π«Ά<action name="ToggleOmnipresent" />β toggles omnipresent (visible on all workspaces / sticky) for the focused window. everywhere all at once β¨<action name="ToggleKeybinds" />β stops handling keybinds/mousebinds other thanToggleKeybindsitself. This can be used to allowA-Taband similar keybinds/mousebinds to be delivered to Virtual Machines, VNC clients or nested compositors. A second call will restore all original keybinds/mousebinds.
This action will only affect the window that had keyboard focus when the binding was executed. Thus when switching to another window, all the usual keybinds will function again until switching back to the original window. There can be multiple windows with this mode set. keybind custody battle, but make it cute π
<action name="ToggleTearing" />
Toggles tearing for the focused window, flipping it between enabled and disabled. This overrides the preference (the tearing hint) that comes from the focused window itself, so it's you calling the shots π
Needs the config optionallowTearingto be on, otherwise this does nothing. And whenallowTearingis set tofullscreenorfullscreenForced, tearing will still only be enabled if the active window is in fullscreen mode β no sneaky windowed tearing, bestie.
<action name="FocusOutput" output="HDMI-A-1" direction="value" wrap="no" />
Gives focus to the topmost window on another output, and warps the cursor to the center of that window. Very "take me to the other screen" energy π¦
outputβ if you specify it, focus goes to that exact output anddirectionis just ignored, like, completely.directionβ ifoutputis omitted, this can be one of"left","right","up"or"down", meaning focus should go to the next output in that direction (if one even exists π).wrap[yes|no]β when you're using thedirectionattribute, wrap around from right-to-left or top-to-bottom, and vice versa. Default isno.
If the target output doesn't contain any windows, the cursor will just be centered on the output. Iconic, minimal, still works π
<action name="MoveToOutput" output="HDMI-A-1" direction="value" wrap="no" />
Moves the active window to another output β unless the window state is fullscreen, in which case, nope, it stays put π«Ά
outputβ if specified, the window gets sent straight to that output anddirectionis ignored.directionβ ifoutputis omitted, it may be one of"left","right","up"or"down", meaning the window should be moved to the next output in that direction (if one exists).wrap[yes|no]β when using thedirectionattribute, wrap around from right-to-left or top-to-bottom, and vice versa. Default isno.
<action name="FitToOutput" />
Resizes the active window's size to the width and height of the output β but only when the window size exceeds the output size. So it's a "you're too big for this screen, bestie, sit down" action πβ¨
<action name="GoToDesktop" to="value" wrap="yes" toggle="no" />
Switches to a workspace. The classic. The main character move π
toβ the workspace to switch to. Supported values are"current","last","left","right","left-occupied","right-occupied", or the full name of a workspace, or its index (starting at1) as configured inrc.xml.wrap[yes|no]β wrap around from last desktop to first, and vice versa. Default isyes.toggle[yes|no]β toggles toβlastβif you're already on the workspace that would be the actual destination. Default isno.
<action name="SendToDesktop" to="value" follow="yes" wrap="yes" />
Sends the active window to a workspace. Not you moving β the window moving. Big difference π
toβ the workspace to send the window to. Supported values are the same as forGoToDesktop.follow[yes|no]β also switch to the specified workspace. Default isyes.wrap[yes|no]β wrap around from last desktop to first, and vice versa. Default isyes.
<action name="VirtualOutputAdd" output_name="value" />
Adds a virtual output (headless backend). Okay this one is lowkey the coolest thing on the whole page, stay with me π§
For example, it can be used to overlay a virtual output on a real output, but with a different resolution (this can be done with wlr-randr or wdisplays). After that, the virtual output can be selected for screen sharing (casting), effectively sharing only that region of the screen. Selective sharing, we love to see it π
It must be noted that overlaying a virtual output and a real output is not endorsed or explicitly supported by wlroots. For example, after configuring the virtual output, the real output must be reconfigured as well (for the overlay configuration to work correctly). This is the example configuration:
<keybind key="W-v">
<action name="VirtualOutputAdd" output_name="ScreenCasting" />
<action name="Execute" command='sh -c "wlr-randr --output ScreenCasting --pos 0,0 --scale 2 --custom-mode 3840x2110; wlr-randr --output eDP-1 --pos 0,0 --scale 2 --mode 3840x2160"' />
</keybind>
<keybind key="W-c">
<action name="VirtualOutputRemove" />
</keybind>
Note that the vertical resolution of "ScreenCasting" output is just 50px smaller than "eDP-1" output, to cut off the bottom panel from screen sharing. Tiny difference, huge payoff π₯
Virtual output is also useful for extending the desktop to (maybe mobile) remote systems like tablets. E.g. simply adding a virtual output, attaching wayvnc to it and running a VNC client on the remote system. Tablet second-screen era π«Ά
output_nameβ the name of the virtual output. Providing a virtual output name is beneficial for further automation. Default is"HEADLESS-X".
<action name="VirtualOutputRemove" output_name="value" />
Removes a virtual output (headless backend). Bye bestie π
output_nameβ the name of the virtual output. If not supplied, it will remove the last virtual output added.
<action name="AutoPlace" policy="value" />
Repositions the window according to the placement policy you want. You're the placement director now π¬
policy[automatic|cursor|center|cascade]β use the specified policy, which has the same meaning as the corresponding value for<placement><policy>. Default isautomatic.
<action name="Shade" />
<action name="Unshade" />
<action name="ToggleShade" />
Set, unset, or toggle, respectively, the "shaded" state of the active window. When shaded, the window contents are hidden, leaving only the titlebar visible β like rolling up a lil window blind, hence the name, iykyk π
Full-screen windows, or those without server-side decorations (including those for which the server-side titlebar has been hidden), are not eligible for shading. Sorry, no shading for you π
<action name="WarpCursor" to="output" x="center" y="center" />
Warps the cursor to a position relative to the active output or window. Teleportation but make it a keybind β¨
to[output|window]β specifies the target area of the warp. Default is"output".x[center|value]β specifies the horizontal warp position within the target area."center": moves the cursor to the horizontal center of the target area. Positive or negative integers warp the cursor to a position offset by the specified number of pixels from the left or right edge of the target area, respectively. Default is"center".y[center|value]β the equivalent for the vertical warp position within the target area. Default is"center".
<action name="HideCursor" />
Hides the pointer or stylus cursor. The cursor becomes visible again on following pointer actions, stylus actions or touchpad gestures β so it's not gone forever, it's just shy π
Use together with the WarpCursor action to not just hide the cursor but to additionally move it away, to prevent e.g. hover effects. Chef's kiss combo π
<action name="EnableScrollWheelEmulation" />
<action name="DisableScrollWheelEmulation" />
<action name="ToggleScrollWheelEmulation">
Enable, disable or toggle scroll wheel emulation on cursor motion, respectively. This can be useful for trackball mouses, to use the rotating ball not just for moving the cursor, but also for (mouse wheel) scrolling. Trackball girlies, this one's for you π«Ά
See also <libinput><scrollFactor> in labwc-config(5) for fine tuning the scroll speed.
<action name="EnableTabletMouseEmulation" />
<action name="DisableTabletMouseEmulation" />
<action name="ToggleTabletMouseEmulation">
Enable, disable or toggle mouse emulation for drawing tablets, respectively. Drawing tablet? Living its best mouse life π
<action name="ToggleMagnify">
Toggles the screen magnifier on or off at the last magnification level used. Picks up right where you left off, respectful queen π
<action name="ToggleShowDesktop" />
Minimizes all windows in the current workspace so that the desktop becomes visible. On calling the action again, the hidden windows are unminimized β provided that, since the initial ShowDesktop:
- (a) no windows have been unminimized;
- (b) workspaces have not been switched; and
- (c) no new applications have been started.
Break any of those and it's not going back to how it was, bestie π
<action name="ZoomIn">
<action name="ZoomOut">
Increase or decrease the magnification level for the screen magnifier. If the magnifier is currently off, ZoomIn will enable it at the lowest magnification, equal to (1 + the magnifier increment set in the theme). If the magnifier is on and at the lowest magnification, ZoomOut will turn it off. Round and round we go πΈ
<action name="None" />
If used as the only action for a binding: clears an earlier defined binding. The polite way to say "never mind" π
<action name="DebugToggleKeyStateIndicator" />
Toggles visibility of the key-state on-screen display (OSD).
Note: this is for debugging purposes only. It's giving developer tools, not lifestyle π
π CONDITIONAL ACTIONS π
Okay so these are the boss-level actions: actions that run other actions. Meta, right? You use them inside keyboard/mouse bindings. It's giving "if this then that" but make it window manager π
π¦ <action name="If">
This is the big one. It runs one set of actions if the focused window matches your criteria, and a totally different set if it doesn't. Like a vibe check for your window, bestie.
The arguments are as follows:
<action name="If">
<query />
<prompt message="" />
<then><action /></then>
<else><action /></else>
</action>
πΈ query
Defines a query with zero or more conditions. All conditions have to evaluate as true for the window to match this query β no partial credit, it's all or nothing. You can define multiple queries, too.
Pattern matching goes according to glob(7) and is case-insensitive. Slay.
The conditions are as follows:
identifierβ the XDG shell app_id for Wayland clients, orWM_CLASSfor XWayland clients.titleβ the XDG shell title for Wayland clients, orWM_NAMEfor XWayland clients.typeβ internal heuristics for Wayland clients,NET_WM_WINDOW_TYPEfor XWayland clients.shaded[yes|no] β whether or not the client is rolled up.maximized[both|horizontal|vertical|none] β whether the client is maximized along both axes, just the horizontal axis, just the vertical axis, or neither axis (none).iconified[yes|no] β whether or not the client is iconified.focused[yes|no] β whether or not the client is focused.omnipresent[yes|no] β whether or not the client is visible on all desktops.desktopβ the desktop the client is currently on. This can be the number or name of a desktop, or the special relative values"current","other","left","right","left-occupied","right-occupied"or"last". Heads up: the"left","right","left-occupied"and"right-occupied"directions will not wrap. No looping around, bestie π«Άtiled[up|right|down|left|up-left|up-right|down-left|down-right|center|any] β whether the client is tiled (snapped) along the indicated screen edge.tiled_regionβ whether the client is tiled (snapped) to the indicated region. And the indicated region may be a glob, so go wild β¨decoration[full|border|none] β whether the client has full server-side decorations, borders only, or no server-side decorations at all.monitor[current|left|right|<monitor_name>] β whether the client is on a monitor relative to the currently focused monitor (current,left, orright), or on a monitor with the supplied<monitor_name>.
This argument is optional. π«
π prompt
Displays a yes/no prompt dialog (labnag by default). If "yes" is selected, the then branch gets taken; same deal with "no" and else. This argument is optional.
Okay important lore: the syntax here is different to Openbox, where a prompt element isn't tied to If-actions but would just be a child of the downstream action. The reason for the difference is increased flexibility and functionality, gained by optionally using an else branch. iykyk π
<keybind key="W-q">
<action name="If">
<prompt message="Quit?" />
<then>
<action name="Exit" />
</then>
</action>
</keybind>
π then
A list of actions to be executed if the window matches any query. This argument is optional.
π else
A list of actions to be executed if the window does not match any query. This argument is optional.
π <action name="ForEach">
Literally identical to the "If" action, except it applies to all windows, not just the focused one. Main character energy for your entire window list π
The ForEach action has another optional none branch which gets executed when no window has been matched by the query. This lets you do things like implement run-or-raise functionality. No cap, that's a genuinely iconic use case π
β SEE ALSO β
labwc(1), labwc-config(5), labwc-theme(5), glob(7)
That's the whole page, bestie β you made it to the end π This was labwc-actions(5) from 2026-08-22, and honestly? She ate. Go forth and bind your keys with confidence π
β¨π¦
π¦ where this page comes from
- arch rolling: labwc 0.20.2-1 Β· GPL-2.0-only
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms