diff options
author | Paul Tagliamonte <paultag@ubuntu.com> | 2011-09-02 00:22:01 (GMT) |
---|---|---|
committer | Mathias Gumz <akira at fluxbox dot org> | 2011-09-02 02:57:28 (GMT) |
commit | b104d9e4d0fab70dd5bd3119e2808cd3fb02bffa (patch) | |
tree | 180d8b1f9be5698d722a019f65939614caa91f07 /doc/fluxbox-style.5.in | |
parent | 631fd58823798e4d37ef37fd1a9dd02828f4f487 (diff) | |
download | fluxbox-b104d9e4d0fab70dd5bd3119e2808cd3fb02bffa.zip fluxbox-b104d9e4d0fab70dd5bd3119e2808cd3fb02bffa.tar.bz2 |
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.
Diffstat (limited to 'doc/fluxbox-style.5.in')
-rw-r--r-- | doc/fluxbox-style.5.in | 22 |
1 files changed, 14 insertions, 8 deletions
diff --git a/doc/fluxbox-style.5.in b/doc/fluxbox-style.5.in index 2afdeae..ccaa6cb 100644 --- a/doc/fluxbox-style.5.in +++ b/doc/fluxbox-style.5.in | |||
@@ -1,13 +1,13 @@ | |||
1 | '\" t | 1 | '\" t |
2 | .\" Title: fluxbox-style | 2 | .\" Title: fluxbox-style |
3 | .\" Author: [see the "AUTHORS" section] | 3 | .\" Author: Henrik Kinnunen <fluxgen@fluxbox.org> |
4 | .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> | 4 | .\" Generator: DocBook XSL Stylesheets v1.75.2 <http://docbook.sf.net/> |
5 | .\" Date: 02/19/2011 | 5 | .\" Date: 27 February 2011 |
6 | .\" Manual: Fluxbox Manual | 6 | .\" Manual: Fluxbox Manual |
7 | .\" Source: fluxbox-style.txt | 7 | .\" Source: fluxbox-style.txt |
8 | .\" Language: English | 8 | .\" Language: English |
9 | .\" | 9 | .\" |
10 | .TH "FLUXBOX\-STYLE" "5" "02/19/2011" "fluxbox\-style\&.txt" "Fluxbox Manual" | 10 | .TH "FLUXBOX\-STYLE" "5" "27 February 2011" "fluxbox\-style\&.txt" "Fluxbox Manual" |
11 | .\" ----------------------------------------------------------------- | 11 | .\" ----------------------------------------------------------------- |
12 | .\" * Define some portability stuff | 12 | .\" * Define some portability stuff |
13 | .\" ----------------------------------------------------------------- | 13 | .\" ----------------------------------------------------------------- |
@@ -45,9 +45,9 @@ fluxbox(1) uses its own graphics class to render its images on the fly\&. By usi | |||
45 | .sp | 45 | .sp |
46 | A style is made up of a few major components which then have their own sub\-directives\&. The major components are as follows: | 46 | A style is made up of a few major components which then have their own sub\-directives\&. The major components are as follows: |
47 | .sp | 47 | .sp |
48 | 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\&. | 48 | 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\&. |
49 | .sp | 49 | .sp |
50 | 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\&. | 50 | 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\&. |
51 | .sp | 51 | .sp |
52 | A more complete reference to this can be found in X(7), section \fIRESOURCES\fR\&. | 52 | A more complete reference to this can be found in X(7), section \fIRESOURCES\fR\&. |
53 | .SH "LOCATION" | 53 | .SH "LOCATION" |
@@ -129,7 +129,7 @@ This sets the color resource of the menu and all of its \fIchildren\fR to \(oqrg | |||
129 | .sp | 129 | .sp |
130 | 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)\&.) | 130 | 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)\&.) |
131 | .sp | 131 | .sp |
132 | 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: | 132 | 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: |
133 | .sp | 133 | .sp |
134 | .if n \{\ | 134 | .if n \{\ |
135 | .RS 4 | 135 | .RS 4 |
@@ -249,7 +249,7 @@ Of course this could all be placed on one line\&. Also note that for the offset | |||
249 | 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[] | 249 | 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[] |
250 | .SH "FULL COMPONENT LIST" | 250 | .SH "FULL COMPONENT LIST" |
251 | .sp | 251 | .sp |
252 | 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\&. | 252 | 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\&. |
253 | .SH "WINDOW OPTIONS" | 253 | .SH "WINDOW OPTIONS" |
254 | .sp | 254 | .sp |
255 | Many, many things you can do with window design in fluxbox(1), below are your options\&. Have fun\&. | 255 | 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> | |||
529 | .RE | 529 | .RE |
530 | .\} | 530 | .\} |
531 | .sp | 531 | .sp |
532 | See /usr/share/X11/rgb\&.txt for an explaination\&. | 532 | See /usr/share/X11/rgb\&.txt for an explanation\&. |
533 | .SH "AUTHORS" | 533 | .SH "AUTHORS" |
534 | .sp | 534 | .sp |
535 | Blackbox was written and maintained by Brad Hughes <blackbox at alug\&.org> and Jeff Raven <jraven at psu\&.edu>\&. | 535 | 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 | |||
542 | .SH "SEE ALSO" | 542 | .SH "SEE ALSO" |
543 | .sp | 543 | .sp |
544 | fluxbox(1) fbsetbg(1) fbsetroot(1) | 544 | fluxbox(1) fbsetbg(1) fbsetroot(1) |
545 | .SH "AUTHOR" | ||
546 | .PP | ||
547 | \fBHenrik Kinnunen\fR <\&fluxgen@fluxbox\&.org\&> | ||
548 | .RS 4 | ||
549 | Author. | ||
550 | .RE | ||