Rebuilding the fluxbox docs to change fix a small grammer mistake

Fluxbox's man page had "allows to", which should actually be something like
 "allows one to".

 The rest of the .ins were rebuilt as a result. No changes otherwise.
This commit is contained in:
Paul Tagliamonte 2011-09-02 00:22:01 +00:00 committed by Mathias Gumz
parent 631fd58823
commit b104d9e4d0
11 changed files with 138 additions and 87 deletions

View file

@ -560,12 +560,12 @@ The possible tools are:
This displays the name of the current workspace.
*PrevWorkspace*:::
This displays an arrow that allows to switch to the workspace left of the
current one.
This displays an arrow that allows one to switch to the workspace left of
the current one.
*NextWorkspace*:::
This displays an arrow that allows to switch to the workspace right of the
current one.
This displays an arrow that allows one to switch to the workspace right of
the current one.
*PrevWindow*:::
This displays an arrow that switches focus to the previous visible window on

View file

@ -1,13 +1,13 @@
'\" t
.\" Title: fbrun
.\" Author: [see the "AUTHORS" section]
.\" Author: Jim Ramsay <i.am@jimramsay.com>
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 02/19/2011
.\" Date: 18 February 2009
.\" Manual: Fluxbox Manual
.\" Source: fbrun.txt
.\" Language: English
.\"
.TH "FBRUN" "1" "02/19/2011" "fbrun\&.txt" "Fluxbox Manual"
.TH "FBRUN" "1" "18 February 2009" "fbrun\&.txt" "Fluxbox Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@ -128,3 +128,9 @@ It was then converted to asciidoc format by Jim Ramsay <i\&.am at jimramsay\&.co
.SH "SEE ALSO"
.sp
fluxbox(1)
.SH "AUTHOR"
.PP
\fBJim Ramsay\fR <\&i\&.am@jimramsay\&.com\&>
.RS 4
Author.
.RE

View file

@ -1,13 +1,13 @@
'\" t
.\" Title: fbsetbg
.\" Author: [see the "AUTHORS" section]
.\" Author: Jim Ramsay <i.am@jimramsay.com>
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 02/19/2011
.\" Date: 27 February 2011
.\" Manual: Fluxbox Manual
.\" Source: fbsetbg.txt
.\" Language: English
.\"
.TH "FBSETBG" "1" "02/19/2011" "fbsetbg\&.txt" "Fluxbox Manual"
.TH "FBSETBG" "1" "27 February 2011" "fbsetbg\&.txt" "Fluxbox Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@ -152,13 +152,6 @@ $ DISPLAY=:0\&.0 fbsetbg \-l
.if n \{\
.RE
.\}
.SH "ONLINE DOCUMENTATION"
.PP
Much more extensive documentation for \fBfbsetbg(1)\fR is provided on
.RS 4
\m[blue]\fBhttp://www\&.xs4all\&.nl/~hanb/software/fbsetbg/fbsetbg\&.html\fR\m[]
.RE
.SH "BUGS"
.sp
\fBfbsetbg(1)\fR is not foolproof\&.
@ -170,3 +163,9 @@ This manpage was converted to asciidoc format by Jim Ramsay <i\&.am at jimramsay
.SH "SEE ALSO"
.sp
fluxbox(1) fbsetroot(1)
.SH "AUTHOR"
.PP
\fBJim Ramsay\fR <\&i\&.am@jimramsay\&.com\&>
.RS 4
Author.
.RE

View file

@ -1,13 +1,13 @@
'\" t
.\" Title: fbsetroot
.\" Author: [see the "AUTHORS" section]
.\" Author: Jim Ramsay <i.am@jimramsay.com>
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 02/19/2011
.\" Date: 27 February 2011
.\" Manual: Fluxbox Manual
.\" Source: fbsetroot.txt
.\" Language: English
.\"
.TH "FBSETROOT" "1" "02/19/2011" "fbsetroot\&.txt" "Fluxbox Manual"
.TH "FBSETROOT" "1" "27 February 2011" "fbsetroot\&.txt" "Fluxbox Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@ -127,3 +127,9 @@ Further updates for fluxbox\-1\&.1\&.2 and conversion to asciidoc format by Jim
.SH "SEE ALSO"
.sp
fluxbox(1) fbsetbg(1) xsetroot(1) xmessage(1) gxmessage(1)
.SH "AUTHOR"
.PP
\fBJim Ramsay\fR <\&i\&.am@jimramsay\&.com\&>
.RS 4
Author.
.RE

View file

@ -1,13 +1,13 @@
'\" t
.\" Title: fluxbox-apps
.\" Author: [see the "AUTHORS" section]
.\" Author: Jim Ramsay <i.am@jimramsay.com>
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 02/21/2011
.\" Date: 27 February 2011
.\" Manual: Fluxbox Manual
.\" Source: fluxbox-apps.txt
.\" Language: English
.\"
.TH "FLUXBOX\-APPS" "5" "02/21/2011" "fluxbox\-apps\&.txt" "Fluxbox Manual"
.TH "FLUXBOX\-APPS" "5" "27 February 2011" "fluxbox\-apps\&.txt" "Fluxbox Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@ -36,7 +36,7 @@ fluxbox-apps \- per\-window attribute configuration for fluxbox(1)
.sp
Variable parameters are shown in emphasis: \fIargument\fR
.sp
All other characters shown are required verbatim\&. Whitespce is only required to delimit words, but it is fine to add more whitespace\&.
All other characters shown are required verbatim\&. Whitespace is only required to delimit words, but it is fine to add more whitespace\&.
.SH "DESCRIPTION"
.sp
It is possible to force an application to always have the same dimensions, position, and other settings when it is first launched\&. These settings are saved in the \(oqapps\(cq file\&.
@ -82,7 +82,7 @@ These sections begin with a line of the format
.sp
Where the \fIpattern\fR item is optional\&. If specified, this pattern must match for the group to take effect\&. It is common to use non\-window\-specific patterns such as \fB(workspace)\fR here\&. See \fBCLIENT PATTERNS\fR for more details\&.
.sp
This is followed by any number of \fB[app]\fR lines\&. These have a simiar format to the \fB[app]\fR section detailed above in \fBAPP SECTIONS\fR, but do not contain any settings and do not have an associated \fB[end]\fR line\&.
This is followed by any number of \fB[app]\fR lines\&. These have a similar format to the \fB[app]\fR section detailed above in \fBAPP SECTIONS\fR, but do not contain any settings and do not have an associated \fB[end]\fR line\&.
.PP
Like this
.RS 4
@ -619,3 +619,9 @@ Wilbert Berendsen <wbsoft at xs4all nl> (blackbox)
.SH "SEE ALSO"
.sp
fluxbox(1) xprop(1) regex(7)
.SH "AUTHOR"
.PP
\fBJim Ramsay\fR <\&i\&.am@jimramsay\&.com\&>
.RS 4
Author.
.RE

View file

@ -1,13 +1,13 @@
'\" t
.\" Title: fluxbox-keys
.\" Author: [see the "AUTHORS" section]
.\" Author: Jim Ramsay <i.am@jimramsay.com>
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 02/27/2011
.\" Date: 27 February 2011
.\" Manual: Fluxbox Manual
.\" Source: fluxbox-keys.txt
.\" Language: English
.\"
.TH "FLUXBOX\-KEYS" "5" "02/27/2011" "fluxbox\-keys\&.txt" "Fluxbox Manual"
.TH "FLUXBOX\-KEYS" "5" "27 February 2011" "fluxbox\-keys\&.txt" "Fluxbox Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@ -119,7 +119,7 @@ is clicked (pressed and released with no movement in between)
.RS 4
The mouse button
\fIN\fR
is currently held, the binded action is triggered as often as the mouse moves\&.
is currently held, the bound action is triggered as often as the mouse moves\&.
.RE
.sp
There are some special "keys" that let you bind events to non\-keyboard events:
@ -303,7 +303,10 @@ Maximize the current window, equivalent to the window button\&.
\fBMaximizeHorizontal\fR / \fBMaximizeVertical\fR
.RS 4
Maximize the current window in one direction only, leaving the other dimension unchanged\&.
.RE
.PP
\fBFullscreen\fR
.RS 4
Resize the window\(cqs content to fit the whole screen, without any window decoration\&.
.RE
.PP
@ -377,7 +380,9 @@ window is visible on all workspaces\&.
.RS 4
Sets which window decorations will be shown\&.
\fIdecor\fR
has the same format as the \(oq[Deco]\(cq parameter in the apps file\&. See \(oqman fluxbox\(cq section APPLICATIONS for more info\&.
has the same format as the \(oq[Deco]\(cq parameter in the apps file\&. See
\fIfluxbox\-apps(5)\fR
for more info\&.
.RE
.PP
\fBToggleDecor\fR
@ -919,7 +924,7 @@ conditions below\&.
.PP
\fBSome\fR \fIcondition\fR
.RS 4
Retuns
Returns
\fBtrue\fR
if any window on any workspace (not just the currently focused one) matches the
\fIcondition\fR\&.
@ -927,7 +932,7 @@ if any window on any workspace (not just the currently focused one) matches the
.PP
\fBEvery\fR \fIcondition\fR
.RS 4
Retuns
Returns
\fBtrue\fR
if every window on every workspace (not just the current one) matches the
\fIcondition\fR\&.
@ -1306,3 +1311,9 @@ Wilbert Berendsen <wbsoft at xs4all nl> (blackbox)
.SH "SEE ALSO"
.sp
fluxbox(1) xprop(1) xev(1) xkill(1) regex(7)
.SH "AUTHOR"
.PP
\fBJim Ramsay\fR <\&i\&.am@jimramsay\&.com\&>
.RS 4
Author.
.RE

View file

@ -1,13 +1,13 @@
'\" t
.\" Title: fluxbox-menu
.\" Author: [see the "AUTHORS" section]
.\" Author: Jim Ramsay <i.am@jimramsay.com>
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 02/19/2011
.\" Date: 27 February 2011
.\" Manual: Fluxbox Manual
.\" Source: fluxbox-menu.txt
.\" Language: English
.\"
.TH "FLUXBOX\-MENU" "5" "02/19/2011" "fluxbox\-menu\&.txt" "Fluxbox Manual"
.TH "FLUXBOX\-MENU" "5" "27 February 2011" "fluxbox\-menu\&.txt" "Fluxbox Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@ -40,7 +40,7 @@ fluxbox-menu \- fluxbox(1) menu syntax
.sp
Variable parameters are shown in emphasis: \fIargument\fR
.sp
All other characters shown are required verbatim\&. Whitespce is only required to delimit words, but it is fine to add more whitespace\&.
All other characters shown are required verbatim\&. Whitespace is only required to delimit words, but it is fine to add more whitespace\&.
.SH "DESCRIPTION"
.sp
There are two types of menus in fluxbox which can be configured\&.
@ -63,7 +63,7 @@ There are up to four fields in a menu line\&. They are of the form
[\fItag\fR] (\fIlabel\fR) {\fIcommand\fR} <\*(Aqicon\*(Aq>
.RE
.sp
The <\*(Aqicon\*(Aq> field is always optional when show below\&. If specified, the \fIicon\fR will be scaled down and displayed in the menu alongside the text label of the item\&. It must be in \&.xpm or \&.png format\&.
The <\*(Aqicon\*(Aq> field is always optional when shown below\&. If specified, the \fIicon\fR will be scaled down and displayed in the menu alongside the text label of the item\&. It must be in \&.xpm or \&.png format\&.
.sp
Any line that starts with a \fI#\fR or \fI!\fR is considered a comment and ignored by fluxbox\&. Also, in the label/command/filename fields you can escape any character\&. Using \fI\e\e\fR inserts a literal back\-slash into the label/command/filename field\&.
.sp
@ -155,7 +155,7 @@ Inserts a command item into the menu\&. When you select the menu item from the m
\fIcommand\&...\fR
in your
\fB$SHELL\fR
(or /bin/sh if $SHELL is not set)\&. You can use this to launch applications, run shell scripts, etc\&. Since all arguments are passed verbatim to te shell, you can use environment variables, pipes, or anything else the shell can do\&. Note that processes only see environment variables that were set before fluxbox started (such as in ~/\&.fluxbox/startup)\&.
(or /bin/sh if $SHELL is not set)\&. You can use this to launch applications, run shell scripts, etc\&. Since all arguments are passed verbatim to the shell, you can use environment variables, pipes, or anything else the shell can do\&. Note that processes only see environment variables that were set before fluxbox started (such as in ~/\&.fluxbox/startup)\&.
.RE
.SS "Fluxbox Functions"
.PP
@ -515,3 +515,9 @@ Wilbert Berendsen <wbsoft at xs4all nl> (blackbox)
.SH "SEE ALSO"
.sp
fluxbox(1) fluxbox\-keys(5) fluxbox\-apps(5) xkill(1) iconv(1)
.SH "AUTHOR"
.PP
\fBJim Ramsay\fR <\&i\&.am@jimramsay\&.com\&>
.RS 4
Author.
.RE

View file

@ -1,13 +1,13 @@
'\" t
.\" Title: fluxbox-remote
.\" Author: [see the "AUTHORS" section]
.\" Author: Mark Tiefenbruck <mark@fluxbox.org>
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 02/19/2011
.\" Date: 27 February 2011
.\" Manual: Fluxbox Manual
.\" Source: fluxbox-remote.txt
.\" Language: English
.\"
.TH "FLUXBOX\-REMOTE" "1" "02/19/2011" "fluxbox\-remote\&.txt" "Fluxbox Manual"
.TH "FLUXBOX\-REMOTE" "1" "27 February 2011" "fluxbox\-remote\&.txt" "Fluxbox Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@ -57,3 +57,9 @@ This man page written by Mark Tiefenbruck <mark at fluxbox\&.org>
.SH "SEE ALSO"
.sp
fluxbox(1) fluxbox\-keys(5) wmctrl(1)
.SH "AUTHOR"
.PP
\fBMark Tiefenbruck\fR <\&mark@fluxbox\&.org\&>
.RS 4
Author.
.RE

View file

@ -1,13 +1,13 @@
'\" t
.\" Title: fluxbox-style
.\" Author: [see the "AUTHORS" section]
.\" Author: Henrik Kinnunen <fluxgen@fluxbox.org>
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 02/19/2011
.\" Date: 27 February 2011
.\" Manual: Fluxbox Manual
.\" Source: fluxbox-style.txt
.\" Language: English
.\"
.TH "FLUXBOX\-STYLE" "5" "02/19/2011" "fluxbox\-style\&.txt" "Fluxbox Manual"
.TH "FLUXBOX\-STYLE" "5" "27 February 2011" "fluxbox\-style\&.txt" "Fluxbox Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@ -45,9 +45,9 @@ fluxbox(1) uses its own graphics class to render its images on the fly\&. By usi
.sp
A style is made up of a few major components which then have their own sub\-directives\&. The major components are as follows:
.sp
The \fIwindow\&.*\fR directives control the appearance of the window frames, window\&.tab\&.* controls the appearance of the window tabs, \fImenu\&.*\fR controls the appearance of the popup menu that you see when you right click on the desktop\&. \fItoolbar\&.*\fR is the bar you will see at the top or bottom of your screen\&. Finally the \fIslit\&.\e*\fR has options you can use to customize the appearance of the slit\&. However if you don\(cqt set the slit directives specifically, the slit\(cqs appearance is controlled by the toolbar directives instead\&.
The \fIwindow\&.*\fR directives control the appearance of the window frames, \fIwindow\&.tab\&.*\fR controls the appearance of the window tabs, \fImenu\&.*\fR controls the appearance of the popup menu that you see when you right click on the desktop\&. \fItoolbar\&.*\fR is the bar you will see at the top or bottom of your screen\&. Finally the \fIslit\&.*\fR has options you can use to customize the appearance of the slit\&. However if you don\(cqt set the slit directives specifically, the slit\(cqs appearance is controlled by the toolbar directives instead\&.
.sp
To understand how the style mechanism works, it is nice to know a little about how X11 resources work\&. X11 resources consist of a key and a value\&. The key is constructed of several smaller keys (sometimes referred to as children), delimited by a period (\&.)\&. Keys may also contain an asterisk (\e*) to serve as a wildcard, which means that one line of text will match several keys\&. This is useful for styles that are based on one or two colors\&.
To understand how the style mechanism works, it is nice to know a little about how X11 resources work\&. X11 resources consist of a key and a value\&. The key is constructed of several smaller keys (sometimes referred to as children), delimited by a period (\&.)\&. Keys may also contain an asterisk (*) to serve as a wildcard, which means that one line of text will match several keys\&. This is useful for styles that are based on one or two colors\&.
.sp
A more complete reference to this can be found in X(7), section \fIRESOURCES\fR\&.
.SH "LOCATION"
@ -129,7 +129,7 @@ This sets the color resource of the menu and all of its \fIchildren\fR to \(oqrg
.sp
you set the font resource for all keys to this font name all at once (For information about the fonts installed on your system, you can use a program like xfontsel(1), gtkfontsel, or xlsfonts(1)\&.)
.sp
In the last example you will notice the wildcard (\e*) before font\&. In a Fluxbox style you can set a value with a wildcard\&. The example means that every font in the style will be what is specified\&. You can do this with any component/value\&. For example if you wanted all of the text to be one color you would do:
In the last example you will notice the wildcard (*) before font\&. In a Fluxbox style you can set a value with a wildcard\&. The example means that every font in the style will be what is specified\&. You can do this with any component/value\&. For example if you wanted all of the text to be one color you would do:
.sp
.if n \{\
.RS 4
@ -249,7 +249,7 @@ Of course this could all be placed on one line\&. Also note that for the offset
If you have problems installing fonts or getting them to work, you should read the docs page at xfree\&.org\&. Here is a link to one of these: \m[blue]\fBhttp://xfree\&.org/4\&.3\&.0/fonts2\&.html#3\fR\m[]
.SH "FULL COMPONENT LIST"
.sp
Here is the exhaustive component list for fluxbox(1) styles\&. Each one is listed with their type of value required\&. Comments in a style file are preceded with an exclamation point (!) which we also use here so that these can be pasted into a new theme\&.cfg to be customized appropiately\&. Please note that in order to keep styles consistent it is often the practice of stylists to provide all of the theme\-items in their style file even if they are not used\&. This allows the user the ease of changing different components\&.
Here is the exhaustive component list for fluxbox(1) styles\&. Each one is listed with their type of value required\&. Comments in a style file are preceded with an exclamation point (!) which we also use here so that these can be pasted into a new theme\&.cfg to be customized appropriately\&. Please note that in order to keep styles consistent it is often the practice of stylists to provide all of the theme\-items in their style file even if they are not used\&. This allows the user the ease of changing different components\&.
.SH "WINDOW OPTIONS"
.sp
Many, many things you can do with window design in fluxbox(1), below are your options\&. Have fun\&.
@ -529,7 +529,7 @@ rgb:<0\-255>/<0\-255>/<0\-255>
.RE
.\}
.sp
See /usr/share/X11/rgb\&.txt for an explaination\&.
See /usr/share/X11/rgb\&.txt for an explanation\&.
.SH "AUTHORS"
.sp
Blackbox was written and maintained by Brad Hughes <blackbox at alug\&.org> and Jeff Raven <jraven at psu\&.edu>\&.
@ -542,3 +542,9 @@ This manpage was composed from various resources including the official document
.SH "SEE ALSO"
.sp
fluxbox(1) fbsetbg(1) fbsetroot(1)
.SH "AUTHOR"
.PP
\fBHenrik Kinnunen\fR <\&fluxgen@fluxbox\&.org\&>
.RS 4
Author.
.RE

View file

@ -1,13 +1,13 @@
'\" t
.\" Title: fluxbox
.\" Author: [see the "AUTHORS" section]
.\" Author: Henrik Kinnunen <fluxgen@fluxbox.org>
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 02/19/2011
.\" Date: 27 February 2011
.\" Manual: Fluxbox Manual
.\" Source: fluxbox.txt
.\" Language: English
.\"
.TH "FLUXBOX" "1" "02/19/2011" "fluxbox\&.txt" "Fluxbox Manual"
.TH "FLUXBOX" "1" "27 February 2011" "fluxbox\&.txt" "Fluxbox Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@ -74,7 +74,7 @@ Starting fluxbox with this option will designate a file in which you want to log
\fB\-rc\fR \fIrcfile\fR
.RS 4
Use a different config file other than the default
\fB\e~/\&.fluxbox/init\fR\&.
\fB~/\&.fluxbox/init\fR\&.
.RE
.PP
\fB\-v\fR, \fB\-version\fR
@ -103,11 +103,11 @@ Lists all available internal commands\&.
.RE
.SH "STARTING FLUXBOX"
.sp
\fBfluxbox(1)\fR comes with a program called \fBstartfluxbox(1)\fR usually located wherever you installed fluxbox\&. This script provides you with many options and variables that can be set when starting fluxbox\&. To actually call fluxbox and begin using it, you should place \(lqexec startfluxbox\(rq in your \fB~/\&.xinitrc\fR as the last executed command\&. This is assuming that the location of \fBfluxbox(1)\fR and \fBstartfluxbox(1)\fR are in your shell\(cqs $PATH\&. Also note that you may need to create the \fB~/\&.xinitrc\fR file or your setup may use \fB\e~/\&.xsession\fR instead, depending on your X setup\&. Some X login managers like \fBgdm(1)\fR or \fBkdm(1)\fR may simply provide a \(lqFluxbox\(rq session for you without having to alter any settings\&.
\fBfluxbox(1)\fR comes with a program called \fBstartfluxbox(1)\fR usually located wherever you installed fluxbox\&. This script provides you with many options and variables that can be set when starting fluxbox\&. To actually call fluxbox and begin using it, you should place \(lqexec startfluxbox\(rq in your \fB~/\&.xinitrc\fR as the last executed command\&. This is assuming that the location of \fBfluxbox(1)\fR and \fBstartfluxbox(1)\fR are in your shell\(cqs $PATH\&. Also note that you may need to create the \fB~/\&.xinitrc\fR file or your setup may use \fB~/\&.xsession\fR instead, depending on your X setup\&. Some X login managers like \fBgdm(1)\fR or \fBkdm(1)\fR may simply provide a \(lqFluxbox\(rq session for you without having to alter any settings\&.
.sp
By using fluxbox \-i you\(cqll see the defaults used by \fBfluxbox(1)\fR\&. These are what fluxbox looks for upon startup\&. In the list of \(lqDefaults:\(rq you\(cqll see a menu file location, this is where you can provide a system\-wide menu file for your users\&.
.sp
On exit or restart, fluxbox will save user defaults in the file \fB\e~/\&.fluxbox/init\fR\&. Resources in this file can also be edited by hand, see the \fBRESOURCES\fR section for more details\&. \fBfluxbox(1)\fR also has many tools to edit these; look through the main menu once fluxbox has started to find different ways of managing your session\&.
On exit or restart, fluxbox will save user defaults in the file \fB~/\&.fluxbox/init\fR\&. Resources in this file can also be edited by hand, see the \fBRESOURCES\fR section for more details\&. \fBfluxbox(1)\fR also has many tools to edit these; look through the main menu once fluxbox has started to find different ways of managing your session\&.
.SH "USING FLUXBOX"
.sp
When using fluxbox for the first time, users who are more accustomed to full desktop environments such as KDE or Gnome may be a little surprised by the minimal screen content\&. fluxbox is designed to be fast and powerful, so it may take a bit of getting used to \(em however, the rewards are worthwhile\&.
@ -491,9 +491,9 @@ Keyboard bindings:
.IP \(bu 2.3
.\}
\fBWin+1\fR
\(->
\fBWin+9\fR: Select the 1st \(-> 9th tab in the current window
\fBWIN+1\fR
\-
\fBWIN+9\fR: Select the 1st \(-> 9th tab in the current window
.RE
.sp
.RS 4
@ -662,7 +662,7 @@ for a small \(lqrun program\(rq dialog
.\}
\fBCTRL+F1\fR
\(->
\-
\fBCTRL+F12\fR: Switch to the 1st \(-> 12th workspace
.RE
.sp
@ -676,7 +676,7 @@ for a small \(lqrun program\(rq dialog
.\}
\fBWIN+F1\fR
\(->
\-
\fBWIN+F12\fR: Send the current window to a specific workspace
.RE
.sp
@ -690,7 +690,7 @@ for a small \(lqrun program\(rq dialog
.\}
\fBCTRL+WIN+F1\fR
\(->
\-
\fBCTRL+WIN+F12\fR: Take the current window to a specific workspace
.RE
.SH "MENUS"
@ -726,7 +726,7 @@ upon a default install\&. Remember that you can confirm this with fluxbox \-i\&.
\fBUser Styles\fR
.RS 4
This is where your custom styles are listed\&. It will list any styles from
\fB\e~/\&.fluxbox/styles/\fR, which may be styles you grab from the Internet, or your own custom styles, provided you follow the standards described in
\fB~/\&.fluxbox/styles/\fR, which may be styles you grab from the Internet, or your own custom styles, provided you follow the standards described in
\fBfluxbox\-style(5)\fR\&.
.RE
.PP
@ -1054,7 +1054,7 @@ Pops up a dialog to enter a new name for the current workspace\&.
.PP
\fBRemove Last\fR
.RS 4
Remove the last workspace in the list\&. Any windows curretly open there will be sent to the next\-to\-last workspace\&.
Remove the last workspace in the list\&. Any windows currently open there will be sent to the next\-to\-last workspace\&.
.RE
.SH "TOOLBAR"
.sp
@ -1086,12 +1086,12 @@ This displays the name of the current workspace\&.
.PP
\fBPrevWorkspace\fR
.RS 4
This displays an arrow that allows to switch to the workspace left of the current one\&.
This displays an arrow that allows one to switch to the workspace left of the current one\&.
.RE
.PP
\fBNextWorkspace\fR
.RS 4
This displays an arrow that allows to switch to the workspace right of the current one\&.
This displays an arrow that allows one to switch to the workspace right of the current one\&.
.RE
.PP
\fBPrevWindow\fR
@ -1306,14 +1306,14 @@ fluxbox enables you to use specialized files that contain \fBX(1)\fR resources t
The default installation of fluxbox provides some of these style files\&. See \fBfluxbox\-style(5)\fR to accommodate the growing number of style components\&.
.SS "Style Overlay"
.sp
In addition to the style file, the overlay file, whose location is specified by \fBsession\&.screen0\&.styleOverlay\fR (default: \fB\e~/\&.fluxbox/overlay\fR) can be used to set style resources that override all styles\&. For more information about which parts of fluxbox can be controlled by the overlay file, see \fBfluxbox\-style(5)\fR\&.
In addition to the style file, the overlay file, whose location is specified by \fBsession\&.screen0\&.styleOverlay\fR (default: \fB~/\&.fluxbox/overlay\fR) can be used to set style resources that override all styles\&. For more information about which parts of fluxbox can be controlled by the overlay file, see \fBfluxbox\-style(5)\fR\&.
.SH "THE SLIT"
.sp
The slit is a special fluxbox window frame that can contain dockable applications, such as \(lqbbtools\(rq or \(lqwindow maker dockapps\(rq\&.
.sp
When applications are run in the slit they have no window borders of their own; instead they are framed in the slit, and they are always visible in the current workspace\&.
.sp
Most dockable applications use the \-w option to run in the slit\&. For example, you could put in your \fB\e~/\&.fluxbox/startup\fR:
Most dockable applications use the \-w option to run in the slit\&. For example, you could put in your \fB~/\&.fluxbox/startup\fR:
.sp
.if n \{\
.RS 4
@ -1368,15 +1368,15 @@ This sets the alpha value for the slit\&. Use the left mouse button to decrease
\fBClients\fR
.RS 4
This submenu lets you reorder the the applications running in the slit\&. You are able to hide apps from the slit by unselecting them in the list showing\&. This will not kill the app\&. You can make them re\-appear by selecting them in the list\&. The "Save SlitList" option saves the new order to you slitlist located in
\fB\e~/\&.fluxbox/slitlist\fR\&. See the next section for details\&.
\fB~/\&.fluxbox/slitlist\fR\&. See the next section for details\&.
.RE
.SS "Slitlist File"
.sp
fluxbox\(cqs slitlist file is available for those that use dockapps in the slit\&. This file helps fluxbox keep track of the \fBorder\fR of the dockapps when in the slit\&. The file is generally located at \fB\e~/\&.fluxbox/slitlist\fR\&.
fluxbox\(cqs slitlist file is available for those that use dockapps in the slit\&. This file helps fluxbox keep track of the \fBorder\fR of the dockapps when in the slit\&. The file is generally located at \fB~/\&.fluxbox/slitlist\fR\&.
.sp
A simple procedure for getting the slit sequences the way you like it is: 1\&. Run fluxbox with no pre\-loaded dockapps 2\&. Run dockapps individually in the order you want them 3\&. Add dockapps to your \fBstartfluxbox(1)\fR script
.sp
This sequence will be saved by default to \fB\e~/\&.fluxbox/slitlist\fR and will be remembered for future instances of fluxbox\&.
This sequence will be saved by default to \fB~/\&.fluxbox/slitlist\fR and will be remembered for future instances of fluxbox\&.
.sp
Users are free to manually edit the slitlist file\&. It is a simple list of window names, as given by \fBxprop(1)\fR, one per dockapp\&. Similar to the init file it should not be edited while fluxbox is running\&. Otherwise changes may get overwritten\&.
.sp
@ -1456,7 +1456,7 @@ There are two ways to assign a window to a different layer\&. When the window is
The other way to set the layer for a window is through the \(oqapps\(cq file\&. This method is described in \fBfluxbox\-apps(5)\fR\&.
.SH "RESOURCES"
.sp
Usually the \fB\e~/\&.fluxbox/init\fR resource file is created and maintained by fluxbox itself\&. You can use the \fBConfigure Menu\fR, mentioned above, to set most of these options\&. However, we\(cqll cover all of the resource options that are available to the user\&. If you edit this file while fluxbox is running, you must \(lqreconfigure\(rq to reload the resource options\&.
Usually the \fB~/\&.fluxbox/init\fR resource file is created and maintained by fluxbox itself\&. You can use the \fBConfigure Menu\fR, mentioned above, to set most of these options\&. However, we\(cqll cover all of the resource options that are available to the user\&. If you edit this file while fluxbox is running, you must \(lqreconfigure\(rq to reload the resource options\&.
.sp
When running fluxbox in a multiple\-screen environment the screen0 key can also be screen1, screen2, to customize the behavior of fluxbox on each desktop accordingly\&. Here are the resources that are currently available:
.PP
@ -1975,7 +1975,7 @@ Default right:
\fBShade Minimize Maximize Close\fR
.RE
.sp
All of the \fIlocation\fR resources following require a pathname to their specific files\&. This is where you can specify different files\&. Most of the defaults will be located in the user\(cqs \fB\e~/\&.fluxbox\fR directory\&.
All of the \fIlocation\fR resources following require a pathname to their specific files\&. This is where you can specify different files\&. Most of the defaults will be located in the user\(cqs \fB~/\&.fluxbox\fR directory\&.
.PP
\fBsession\&.appsFile\fR: \fIlocation\fR
.RS 4
@ -2032,7 +2032,7 @@ for details\&.
\fBsession\&.screen0\&.windowMenu\fR: \fIlocation\fR
.RS 4
This optionally specifies the location of a user\-defined window menu\&. If left blank, it will use
\fB\e~/\&.fluxbox/windowmenu\fR\&.
\fB~/\&.fluxbox/windowmenu\fR\&.
.sp
Default:
\fBblank\fR
@ -2190,3 +2190,9 @@ If you find any bugs, please visit the #fluxbox irc channel on irc\&.freenode\&.
.SH "SEE ALSO"
.sp
fluxbox\-apps(5) fluxbox\-keys(5) fluxbox\-style(5) fluxbox\-menu(5) fluxbox\-remote(1) fbsetroot(1) fbsetbg(1) fbrun(1) startfluxbox(1)
.SH "AUTHOR"
.PP
\fBHenrik Kinnunen\fR <\&fluxgen@fluxbox\&.org\&>
.RS 4
Author.
.RE

View file

@ -1,13 +1,13 @@
'\" t
.\" Title: startfluxbox
.\" Author: [see the "AUTHORS" section]
.\" Author: Jim Ramsay <i.am@jimramsay.com>
.\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/>
.\" Date: 02/19/2011
.\" Date: 27 February 2011
.\" Manual: Fluxbox Manual
.\" Source: startfluxbox.txt
.\" Language: English
.\"
.TH "STARTFLUXBOX" "1" "02/19/2011" "startfluxbox\&.txt" "Fluxbox Manual"
.TH "STARTFLUXBOX" "1" "27 February 2011" "startfluxbox\&.txt" "Fluxbox Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@ -34,18 +34,18 @@ startfluxbox \- start a fluxbox session
\fBstartfluxbox\fR
.SH "DESCRIPTION"
.sp
\fBstartfluxbox\fR is a script which runs the file \fB\e~/\&.fluxbox/startup\fR If it doesn\(cqt exist it will be generated\&.
\fBstartfluxbox\fR is a script which runs the file \fB~/\&.fluxbox/startup\fR If it doesn\(cqt exist it will be generated\&.
.sp
\fBstartfluxbox\fR should be started from your \fB~/\&.xinitrc\fR if you use startx, or \fB\e~/\&.xsession\fR if you run a display manager, like xdm\&.
\fBstartfluxbox\fR should be started from your \fB~/\&.xinitrc\fR if you use startx, or \fB~/\&.xsession\fR if you run a display manager, like xdm\&.
.SH "FILES"
.PP
\fB\e~/\&.fluxbox/startup\fR
\fB~/\&.fluxbox/startup\fR
.RS 4
This file contains all commands that should be executed before fluxbox is started\&. The initial file contains helpful comments for beginners\&. It also starts fluxbox\&.
.RE
.SH "EXAMPLES"
.sp
The default \fB\e~/\&.fluxbox/startup\fR is as follows:
The default \fB~/\&.fluxbox/startup\fR is as follows:
.sp
.if n \{\
.RS 4
@ -104,13 +104,6 @@ wait $fbpid
So xsetroot, ipager, and gkrellm2 will all be started after fluxbox, after giving fluxbox 1 second to startup\&.
.sp
For more details on what else you can do in this script, see \fBsh(1p)\fR, or the documentation for your shell\&.
.SH "ONLINE DOCUMENTATION"
.PP
More extensive documentation for \fBstartfluxbox(1)\fR can be found at
.RS 4
\m[blue]\fBhttp://www\&.xs4all\&.nl/~hanb/software/fluxbox/startfluxbox\&.html\fR\m[]
.RE
.SH "AUTHORS"
.sp
The author of \fBstartfluxbox(1)\fR is Han Boetes <han at fluxbox\&.org>
@ -119,3 +112,9 @@ This manpage was converted to asciidoc format by Jim Ramsay <i\&.am at jimramsay
.SH "SEE ALSO"
.sp
fluxbox(1)
.SH "AUTHOR"
.PP
\fBJim Ramsay\fR <\&i\&.am@jimramsay\&.com\&>
.RS 4
Author.
.RE