aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorSlava Semushin <php-coder@altlinux.ru>2008-02-06 17:48:20 (GMT)
committerHenrik Kinnunen <fluxgen@fluxbox.org>2008-05-07 06:01:38 (GMT)
commita9ae7533e88dce8a05e5b3b059a85c43e811ac90 (patch)
tree9ef75422eb7191880b11adecf299a0f0f9897197 /doc
parent4d0dba57f0500bc71cbb408d2272dc832ff566f1 (diff)
downloadfluxbox-a9ae7533e88dce8a05e5b3b059a85c43e811ac90.zip
fluxbox-a9ae7533e88dce8a05e5b3b059a85c43e811ac90.tar.bz2
fluxstyle.1: fixed typo which prevent substitution for path to styles directory.
In doc/Makefile.am replaces @pkgdatadir@ string, not @pkg_datadir@. Signed-off-by: Slava Semushin <php-coder@altlinux.ru>
Diffstat (limited to 'doc')
-rw-r--r--doc/asciidoc/fluxstyle.12
-rw-r--r--doc/asciidoc/fluxstyle.txt2
-rw-r--r--doc/fluxstyle.1.in2
3 files changed, 3 insertions, 3 deletions
diff --git a/doc/asciidoc/fluxstyle.1 b/doc/asciidoc/fluxstyle.1
index 92a999a..2e40e5d 100644
--- a/doc/asciidoc/fluxstyle.1
+++ b/doc/asciidoc/fluxstyle.1
@@ -34,7 +34,7 @@ To understand how the style mechanism works, it is nice to know a little about h
34A more complete reference to this can be found in X(7), section \fIRESOURCES\fR. 34A more complete reference to this can be found in X(7), section \fIRESOURCES\fR.
35.sp 35.sp
36.SH "LOCATION" 36.SH "LOCATION"
37There are many places to store your styles, the most common is in your \fI~/.fluxbox/styles\fR directory. The initial installation will place the default styles in \fI@pkg_datadir@/styles\fR providing a basic usable configuration. 37There are many places to store your styles, the most common is in your \fI~/.fluxbox/styles\fR directory. The initial installation will place the default styles in \fI@pkgdatadir@/styles\fR providing a basic usable configuration.
38.sp 38.sp
39When creating your own style, create a directory (normally the name of your style) in \fI~/.fluxbox/styles/\fR (If the \fIstyles\fR directory doesn't exist, create that also). While there isn't an official structure, it is common to create a directory named after your style and place your pixmaps directory (if required) in there along with a file called theme.cfg (may also be named style.cfg). This file is where you will construct your style using the components covered later in this manual page. An example of steps taken when beginning a style project of your own may look like: 39When creating your own style, create a directory (normally the name of your style) in \fI~/.fluxbox/styles/\fR (If the \fIstyles\fR directory doesn't exist, create that also). While there isn't an official structure, it is common to create a directory named after your style and place your pixmaps directory (if required) in there along with a file called theme.cfg (may also be named style.cfg). This file is where you will construct your style using the components covered later in this manual page. An example of steps taken when beginning a style project of your own may look like:
40.sp 40.sp
diff --git a/doc/asciidoc/fluxstyle.txt b/doc/asciidoc/fluxstyle.txt
index d17112e..9f70719 100644
--- a/doc/asciidoc/fluxstyle.txt
+++ b/doc/asciidoc/fluxstyle.txt
@@ -60,7 +60,7 @@ LOCATION
60-------- 60--------
61There are many places to store your styles, the most common is in your 61There are many places to store your styles, the most common is in your
62'~/.fluxbox/styles' directory. The initial installation will place the default 62'~/.fluxbox/styles' directory. The initial installation will place the default
63styles in '@pkg_datadir@/styles' providing a basic usable configuration. 63styles in '@pkgdatadir@/styles' providing a basic usable configuration.
64 64
65When creating your own style, create a directory (normally the name of your 65When creating your own style, create a directory (normally the name of your
66style) in '~/.fluxbox/styles/' (If the 'styles' directory doesn't exist, 66style) in '~/.fluxbox/styles/' (If the 'styles' directory doesn't exist,
diff --git a/doc/fluxstyle.1.in b/doc/fluxstyle.1.in
index 92a999a..2e40e5d 100644
--- a/doc/fluxstyle.1.in
+++ b/doc/fluxstyle.1.in
@@ -34,7 +34,7 @@ To understand how the style mechanism works, it is nice to know a little about h
34A more complete reference to this can be found in X(7), section \fIRESOURCES\fR. 34A more complete reference to this can be found in X(7), section \fIRESOURCES\fR.
35.sp 35.sp
36.SH "LOCATION" 36.SH "LOCATION"
37There are many places to store your styles, the most common is in your \fI~/.fluxbox/styles\fR directory. The initial installation will place the default styles in \fI@pkg_datadir@/styles\fR providing a basic usable configuration. 37There are many places to store your styles, the most common is in your \fI~/.fluxbox/styles\fR directory. The initial installation will place the default styles in \fI@pkgdatadir@/styles\fR providing a basic usable configuration.
38.sp 38.sp
39When creating your own style, create a directory (normally the name of your style) in \fI~/.fluxbox/styles/\fR (If the \fIstyles\fR directory doesn't exist, create that also). While there isn't an official structure, it is common to create a directory named after your style and place your pixmaps directory (if required) in there along with a file called theme.cfg (may also be named style.cfg). This file is where you will construct your style using the components covered later in this manual page. An example of steps taken when beginning a style project of your own may look like: 39When creating your own style, create a directory (normally the name of your style) in \fI~/.fluxbox/styles/\fR (If the \fIstyles\fR directory doesn't exist, create that also). While there isn't an official structure, it is common to create a directory named after your style and place your pixmaps directory (if required) in there along with a file called theme.cfg (may also be named style.cfg). This file is where you will construct your style using the components covered later in this manual page. An example of steps taken when beginning a style project of your own may look like:
40.sp 40.sp