Input Devices

Device Configuration

The global settings below apply to every device of the corresponding type. Per-device overrides are covered in the Device Rules section at the end of this page.

Keyboard Settings

Control key repeat rates and layout rules.

Example:

repeat_rate=40
repeat_delay=300
numlockon=1
xkb_rules_layout=us,de
xkb_rules_variant=dvorak
xkb_rules_options=caps:escape,ctrl:nocaps

Mouse Settings

Configuration for external mice.

Trackpad Settings

Specific settings for laptop touchpads. Some settings may require a relogin to take effect.

Touchscreen Settings

Settings for touchscreen devices. Touch input is forwarded to clients that support the wl_touch protocol; otherwise it falls back to mouse emulation so the touchscreen keeps working with non-touch clients.

Detailed descriptions:

• scroll_button values (use mouse_scroll_button / trackpad_scroll_button):

  • 272 — Left button.
  • 273 — Right button.
  • 274 — Middle button.
  • 275 — Side button.
  • 276 — Extra button.
  • 277 — Forward button.
  • 278 — Back button.
  • 279 — Task button.

• scroll_method values (use mouse_scroll_method / trackpad_scroll_method):

  • 0 — Never send scroll events (no scrolling).
  • 1 — Two-finger scrolling: send scroll events when two fingers are logically down on the device.
  • 2 — Edge scrolling: send scroll events when a finger moves along the bottom or right edge.
  • 4 — Button scrolling: send scroll events when a button is held and the device moves along a scroll axis.

• click_method values (use mouse_click_method / trackpad_click_method):

  • 0 — No software click emulation.
  • 1 — Button areas: use software-defined areas on the touchpad to generate button events.
  • 2 — Clickfinger: the number of fingers determines which button is pressed.

• mouse_accel_profile or trackpad_scroll_profile values:

  • 0 — No acceleration.
  • 1 — Flat: no dynamic acceleration. Pointer speed = original input speed × (1 + mouse_accel_speed).
  • 2 — Adaptive: slow movement results in less acceleration, fast movement results in more.

• button_map values:

  • 0 — 1/2/3 finger tap maps to left / right / middle.
  • 1 — 1/2/3 finger tap maps to left / middle / right.

• send_events_mode values (use mouse_send_events_mode / trackpad_send_events_mode):

  • 0 — Send events from this device normally.
  • 1 — Do not send events from this device.
  • 2 — Disable this device when an external pointer device is plugged in.

Keyboard Layout Switching

To bind multiple layouts and toggle between them, define the layouts in xkb_rules_layout and use xkb_rules_options to set a toggle key combination. Then bind switch_keyboard_layout to trigger a switch.

# Define two layouts: US QWERTY and US Dvorak
xkb_rules_layout=us,us
xkb_rules_variant=,dvorak
xkb_rules_options=grp:lalt_lshift_toggle

Or bind it manually to a key:

# Bind Alt+Shift_L to cycle keyboard layout
bind=alt,shift_l,switch_keyboard_layout

Use mmsg get keyboardlayout to query the current layout.

Input Method Editor (IME)

To use Fcitx5 or IBus, set these environment variables in your config file.

Info: These settings require a restart of the window manager to take effect.

For Fcitx5:

env=GTK_IM_MODULE,fcitx
env=QT_IM_MODULE,fcitx
env=QT_IM_MODULES,wayland;fcitx
env=SDL_IM_MODULE,fcitx
env=XMODIFIERS,@im=fcitx
env=GLFW_IM_MODULE,ibus

For IBus:

env=GTK_IM_MODULE,ibus
env=QT_IM_MODULE,ibus
env=XMODIFIERS,@im=ibus

Device Rules (Advanced)

The global settings above apply to every device of the corresponding type. Use devicerule to override parameters for a specific device.

Finding device names:

The easiest way to get a device's name is to watch for it: run

mmsg watch all-devices

then use the device (type on a keyboard, move a mouse, scroll a touchpad). Each event prints the name of the device that triggered it, so you can match every physical device to its name without guessing. mmsg get all-devices also lists all connected devices at once if you prefer.

Syntax:

devicerule=name:<device-name>,option:value,option:value
devicerule=type:<device-type>,option:value

Put the printed name after name: (the identifier field, vendor:product:name, also works). Use type: to match all devices of a type: keyboard, pointer, touchpad, touch, switch, tablet, pad.

Exact name: matches take priority over type: matches; the first matching rule wins. A rule with keyboard options (kb_*, repeat_*) turns that keyboard into an independent keyboard with its own keymap and repeat settings; unmatched devices stay in the shared, synchronized keyboard group.

Examples:

devicerule=name:AT Translated Set 2 keyboard,kb_layout:ru
devicerule=name:A4Tech USB Mouse,natural_scrolling:1,accel_speed:0.1
devicerule=type:touchpad,tap_to_click:1

Apply changes with mmsg dispatch reload_config or restart mango.

Rule Options

All options are optional; unset options fall back to the global settings. Keyboard kb_* options are independent of the global xkb_rules_* settings: a rule's keymap is compiled only from the options it sets (unset fields use the XKB defaults), so a rule like kb_layout:pt is not affected by a global xkb_rules_variant.

Info: If a rule's keyboard layout fails to compile (e.g. kb_layout:ru with kb_variant:dvorak), mango logs an error and falls back to the global layout instead of crashing.