blob: 220f794e7cd9694d063b939b973c7dd73ade5ec1 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
|
fluxbox-remote(1)
===============
Mark Tiefenbruck <mark@fluxbox.org>
v1.0.0, 6 August, 2008
NAME
----
fluxbox-remote - command line access to key commands for fluxbox(1)
SYNOPSIS
--------
*fluxbox-remote* 'command'
DESCRIPTION
-----------
'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'.
SEE ALSO
--------
fluxbox(1), fluxbox-keys(5), wmctrl(1)
|
