aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJim Ramsay <i.am@jimramsay.com>2009-02-20 16:37:23 (GMT)
committerJim Ramsay <i.am@jimramsay.com>2009-05-26 20:16:07 (GMT)
commitce1fb1cf8e56f21051e15257e8198d7a5c5b49e5 (patch)
tree679eddac01ce1864b8fe300c6e4c3dcd5e588ee3
parentf68ff84bd1fd579bf9940e7edd9777c54aee1d11 (diff)
downloadfluxbox_paul-ce1fb1cf8e56f21051e15257e8198d7a5c5b49e5.zip
fluxbox_paul-ce1fb1cf8e56f21051e15257e8198d7a5c5b49e5.tar.bz2
Added note on ChangeWorkspace
-rw-r--r--doc/asciidoc/fluxbox-keys.txt9
-rw-r--r--doc/fluxbox-keys.5.in15
2 files changed, 19 insertions, 5 deletions
diff --git a/doc/asciidoc/fluxbox-keys.txt b/doc/asciidoc/fluxbox-keys.txt
index 9edb22b..968f4b7 100644
--- a/doc/asciidoc/fluxbox-keys.txt
+++ b/doc/asciidoc/fluxbox-keys.txt
@@ -90,10 +90,13 @@ name is *Mouse*'n' where 'n' is the number of the mouse button. For example,
90events, in normal configurations. *xev(1)* can also be used to tell the button 90events, in normal configurations. *xev(1)* can also be used to tell the button
91number. 91number.
92 92
93////////////////
94There are some special "keys" that let you bind events to non-keyboard events::: 93There are some special "keys" that let you bind events to non-keyboard events:::
95*ChangeWorkspace*;; 94*ChangeWorkspace*;;
96 Fires when the workspace changes 95 Fires when the workspace changes. This can be used to change backgrounds or
96 do anything else you like when you switch to a new workspace. See the
97 *EXAMPLES* below for one idea.
98
99////////////////
97TODO: Advanced users only? 100TODO: Advanced users only?
98*FocusIn* / *FocusOut*;; 101*FocusIn* / *FocusOut*;;
99 Fires when the focus is given to or removed from a window. It may be 102 Fires when the focus is given to or removed from a window. It may be
@@ -103,8 +106,8 @@ TODO: Advanced users only?
103 Fires when the mouse cursor enters or leaves a specific area of the 106 Fires when the mouse cursor enters or leaves a specific area of the
104 screen. It may be useful to combine this with the 'On*' modifiers 107 screen. It may be useful to combine this with the 'On*' modifiers
105 detailed above and/or the 'If' command. 108 detailed above and/or the 'If' command.
106
107//////////////// 109////////////////
110
108CHAINING 111CHAINING
109-------- 112--------
110Key bindings can be chained in a fashion similar to Emacs key bindings using the 113Key bindings can be chained in a fashion similar to Emacs key bindings using the
diff --git a/doc/fluxbox-keys.5.in b/doc/fluxbox-keys.5.in
index 24242d0..0ebb147 100644
--- a/doc/fluxbox-keys.5.in
+++ b/doc/fluxbox-keys.5.in
@@ -1,12 +1,12 @@
1.\" Title: fluxbox-keys 1.\" Title: fluxbox-keys
2.\" Author: [see the "AUTHORS" section] 2.\" Author: [see the "AUTHORS" section]
3.\" Generator: DocBook XSL Stylesheets v1.74.0 <http://docbook.sf.net/> 3.\" Generator: DocBook XSL Stylesheets v1.74.0 <http://docbook.sf.net/>
4.\" Date: 02/19/2009 4.\" Date: 02/20/2009
5.\" Manual: Fluxbox Manual 5.\" Manual: Fluxbox Manual
6.\" Source: fluxbox-keys.txt 1.1.2 6.\" Source: fluxbox-keys.txt 1.1.2
7.\" Language: English 7.\" Language: English
8.\" 8.\"
9.TH "FLUXBOX\-KEYS" "5" "02/19/2009" "fluxbox\-keys\&.txt 1\&.1\&.2" "Fluxbox Manual" 9.TH "FLUXBOX\-KEYS" "5" "02/20/2009" "fluxbox\-keys\&.txt 1\&.1\&.2" "Fluxbox Manual"
10.\" ----------------------------------------------------------------- 10.\" -----------------------------------------------------------------
11.\" * (re)Define some macros 11.\" * (re)Define some macros
12.\" ----------------------------------------------------------------- 12.\" -----------------------------------------------------------------
@@ -239,6 +239,17 @@ You may specify a key by its key name (for example, \fBa\fR or \fBspace\fR) or b
239If you don\'t know the name of a key, you can run \fBxev(1)\fR in a terminal, push the key, and see the name in the output\&. If you have some "special" keys that do not produce a key name in the output of \fBxev(1)\fR, you can just use the keycode (NOT the keysym!) in your keys file\&. 239If you don\'t know the name of a key, you can run \fBxev(1)\fR in a terminal, push the key, and see the name in the output\&. If you have some "special" keys that do not produce a key name in the output of \fBxev(1)\fR, you can just use the keycode (NOT the keysym!) in your keys file\&.
240.sp 240.sp
241Commands can also be bound to mouse button presses, for which the proper "key" name is \fBMouse\fR\fIn\fR where \fIn\fR is the number of the mouse button\&. For example, \fBMouse1\fR is the primary button, and \fBMouse4\fR / \fBMouse5\fR are the scroll wheel events, in normal configurations\&. \fBxev(1)\fR can also be used to tell the button number\&. 241Commands can also be bound to mouse button presses, for which the proper "key" name is \fBMouse\fR\fIn\fR where \fIn\fR is the number of the mouse button\&. For example, \fBMouse1\fR is the primary button, and \fBMouse4\fR / \fBMouse5\fR are the scroll wheel events, in normal configurations\&. \fBxev(1)\fR can also be used to tell the button number\&.
242.PP
243There are some special "keys" that let you bind events to non\-keyboard events:
244.RS 4
245.PP
246\fBChangeWorkspace\fR
247.RS 4
248Fires when the workspace changes\&. This can be used to change backgrounds or do anything else you like when you switch to a new workspace\&. See the
249\fBEXAMPLES\fR
250below for one idea\&.
251.RE
252.RE
242.SH "CHAINING" 253.SH "CHAINING"
243.sp 254.sp
244Key bindings can be chained in a fashion similar to Emacs key bindings using the syntax: 255Key bindings can be chained in a fashion similar to Emacs key bindings using the syntax: