fluxbox-remote(1)

fluxbox-remote1

Command line access to key commands for fluxbox(1)

Usage

fluxbox-remote command

Overview

fluxbox-remote(1) is designed to allow scripts to execute most key commands from fluxbox(1). fluxbox-remote(1) will only work with fluxbox(1): its communications with fluxbox(1) are not standardized in any way. It is recommended that a standards-based tool such as wmctrl(1) be used whenever possible, in order for scripts to work with other window managers.

Caveats

fluxbox-remote(1) uses the X11 protocol to communicate with fluxbox(1). Therefore, it is possible for any user with access to the X(7) server to use fluxbox-remote(1). For this reason, several key commands have been disabled. Users should be aware of the security implications when enabling fluxbox-remote(1), especially when using a forwarded X(7) connection.

Resources

session.screen0.allowRemoteActions: <boolean>

This resource in ~/.fluxbox/init must be set to ‘true’ in order for fluxbox-remote(1) to function. Please read the CAVEATS first.

Environment

In order to communicate with fluxbox(1), the DISPLAY environment variable must be set properly. Usually, the value should be ‘:0.0’.

Releases

10 releases since Debian 5.0 (Lenny); the text changed 4 times.

  1. 5.0
  2. 6.0
  3. 7
  4. 8–12
  5. 13–Arch

-display until Debian 5.0 (Lenny); -h until Debian 5.0 (Lenny); -help until Debian 5.0 (Lenny); -i until Debian 5.0 (Lenny); -info until Debian 5.0 (Lenny); -log until Debian 5.0 (Lenny); -rc until Debian 5.0 (Lenny); -screen until Debian 5.0 (Lenny); -v until Debian 5.0 (Lenny); -verbose until Debian 5.0 (Lenny); -version until Debian 5.0 (Lenny).

Authors

This man page written by Mark Tiefenbruck <mark at fluxbox.org>

Author

Mark Tiefenbruck <[email protected]>

Author.

From fluxbox 1.3.7+221+g36f99b92-1 in Arch Linux 2026-11-01. Parsed by carta from the page's man source.