•

-skip-floating: Skip floating views, only focusing tiled ones.

•

-current-tags: Assign the currently focused tags of the destination output to the view.

• Shift
• Control
• Mod1 (Alt)
• Mod3
• Mod4 (Super)
• Mod5
• None

• BTN_LEFT - left mouse button
• BTN_RIGHT - right mouse button
• BTN_MIDDLE - middle mouse button

• -release: if passed activate on key release instead of key press
• -repeat: if passed activate repeatedly until key release; may not be used with -release
• -layout: if passed, a specific layout is pinned to the mapping. When the mapping is checked against a pressed key, this layout is used to translate the key independent of the active layout

• mode: name of the mode for which to create the mapping
• modifiers: one or more of the modifiers listed above, separated by a plus sign (+).
• key: an XKB keysym name as described above
• command: any command that may be run with riverctl

• mode: name of the mode for which to create the mapping
• modifiers: one or more of the modifiers listed above, separated by a plus sign (+).
• button: the name of a Linux input event code as described above
• action: one of the following values:

•

command: any command that may be run with riverctl

• mode: name of the mode for which to create the mapping
• lid|tablet: 'lid switch' and 'tablet mode switch' are supported
• state:

•

command: any command that may be run with riverctl

• -release: if passed unmap the key release instead of the key press
• mode: name of the mode for which to remove the mapping
• modifiers: one or more of the modifiers listed above, separated by a plus sign (+).
• key: an XKB keysym name as described above

• mode: name of the mode for which to remove the mapping
• modifiers: one or more of the modifiers listed above, separated by a plus sign (+).
• button: the name of a Linux input event code as described above

• mode: name of the mode for which to remove the mapping
• lid|tablet: the switch for which to remove the mapping
• state: a state as listed above

The supported action types are:

• float: Make the view floating. Applies only to new views.
• no-float: Don't make the view floating. Applies only to new views.
• ssd: Use server-side decorations for the view. Applies to new and existing views.
• csd: Use client-side decorations for the view. Applies to new and existing views.
• tags: Set the initial tags of the view. Requires the tags as an argument. Applies only to new views.
• output: Set the initial output of the view. Requires the output as an argument. Applies only to new views. The output can be specified either by connector name (such as HDMI-A-1, or DP-2), or by identifier in the form of MAKE MODEL SERIAL, for example for an output with make: HP Inc., model: HP 22w, and serial: CNC93720WF, the identifier would be: HP Inc. HP 22w CNC93720WF. If the make, model, or serial is unknown, the word "Unknown" is used instead.
• position: Set the initial position of the view, clamping to the bounds of the output. Requires x and y coordinates of the view as arguments, both of which must be non-negative. Applies only to new views.
• dimensions: Set the initial dimensions of the view, clamping to the constraints of the view. Requires width and height of the view as arguments, both of which must be non-negative. Applies only to new views.
• fullscreen: Make the view fullscreen. Applies only to new views.
• no-fullscreen: Don't make the view fullscreen. Applies only to new views.

Both float and no-float rules are added to the same list, which means that adding a no-float rule with the same arguments as a float rule will overwrite it. The same holds for ssd and csd, fullscreen and no-fullscreen rules.

If multiple rules in a list match a given view the most specific rule will be applied. For example with the following rules

app-id  title  action
foo     bar    ssd
foo     *      csd
*       bar    csd
*       baz    ssd

If a view is not matched by any rule, river will respect the csd/ssd wishes of the client and may start the view floating based on simple heuristics intended to catch popup-like views.

If a view is started fullscreen or is not floating, then position and dimensions rules will have no effect A view must be matched by a float rule in order for them to take effect.

Possible values:

• top: Prepends the newly spawned view at the top of the stack.
• bottom: Appends the newly spawned view at the bottom of the stack.
• above: Inserts the newly spawned view above the currently focused view.
• below: Inserts the newly spawned view below the currently focused view.
• after <N>: Inserts the newly spawned view after N views in the stack.

Note that the deprecated attach-mode command is aliased to default-attach-mode for backwards compatibility.

• disabled: Moving the cursor does not affect focus. This is the default.
• normal: Moving the cursor over a view will focus that view. Moving the cursor within a view will not re-focus that view if focus has moved elsewhere.
• always: Moving the cursor will always focus whatever view is under the cursor.

If the view to be focused is on an output that does not have focus, focus is switched to that output.

• disabled: Cursor will not be warped. This is the default.
• on-output-change: When a different output is focused, the cursor will be warped to its center.
• on-focus-change: When a different view/output is focused, the cursor will be warped to its center.

• left-right-middle: 1 finger tap equals left click, 2 finger tap equals right click, 3 finger tap equals middle click.
• left-middle-right: 1 finger tap equals left click, 2 finger tap equals middle click, 3 finger tap equals right click.

• none: No scrolling
• two-finger: Scroll by swiping with two fingers simultaneously
• edge: Scroll by swiping along the edge
• button: Scroll with pointer movement while holding down a button