1 |
nightmorph 08/11/06 22:32:46 |
2 |
|
3 |
Modified: fluxbox-config.xml |
4 |
Log: |
5 |
Added new material to the Fluxbox guide on available USE flags, inspired by bug 245893. also some other updates throughout the doc. |
6 |
|
7 |
Revision Changes Path |
8 |
1.32 xml/htdocs/doc/en/fluxbox-config.xml |
9 |
|
10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/fluxbox-config.xml?rev=1.32&view=markup |
11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/fluxbox-config.xml?rev=1.32&content-type=text/plain |
12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/fluxbox-config.xml?r1=1.31&r2=1.32 |
13 |
|
14 |
Index: fluxbox-config.xml |
15 |
=================================================================== |
16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/fluxbox-config.xml,v |
17 |
retrieving revision 1.31 |
18 |
retrieving revision 1.32 |
19 |
diff -u -r1.31 -r1.32 |
20 |
--- fluxbox-config.xml 10 Mar 2008 06:03:41 -0000 1.31 |
21 |
+++ fluxbox-config.xml 6 Nov 2008 22:32:46 -0000 1.32 |
22 |
@@ -1,5 +1,5 @@ |
23 |
<?xml version="1.0" encoding="UTF-8"?> |
24 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/fluxbox-config.xml,v 1.31 2008/03/10 06:03:41 nightmorph Exp $ --> |
25 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/fluxbox-config.xml,v 1.32 2008/11/06 22:32:46 nightmorph Exp $ --> |
26 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
27 |
|
28 |
<guide link="/doc/en/fluxbox-config.xml"> |
29 |
@@ -23,8 +23,8 @@ |
30 |
<!-- See http://creativecommons.org/licenses/by-sa/2.0 --> |
31 |
<license/> |
32 |
|
33 |
-<version>1.10</version> |
34 |
-<date>2008-03-09</date> |
35 |
+<version>1.11</version> |
36 |
+<date>2008-11-06</date> |
37 |
|
38 |
<chapter> |
39 |
<title>Introduction</title> |
40 |
@@ -86,15 +86,49 @@ |
41 |
<body> |
42 |
|
43 |
<p> |
44 |
-Gentoo provides an ebuild to quickly and easily install Fluxbox. While Gentoo |
45 |
-provides the <c>gnome</c> and <c>kde</c> USE flags to give compatibility with |
46 |
-these environments, it has been the author's experience that these USE flags are |
47 |
-not needed. If you desire qt, gtk+, or any KDE/GNOME utility then you are free |
48 |
-to emerge and configure those independently. For example, the author uses |
49 |
-Fluxbox with <c>k3b</c>, the KDE optical disc burning utility. |
50 |
+Before you install Fluxbox, you should take a look at some of the available USE |
51 |
+flags. |
52 |
</p> |
53 |
|
54 |
<p> |
55 |
+While the <c>gnome</c> and <c>kde</c> USE flags are provided to give |
56 |
+compatibility with these environments, it has been the author's experience that |
57 |
+these USE flags are not needed. If you desire qt, gtk+, or any KDE/GNOME utility |
58 |
+then you are free to emerge and configure those independently. The <c>gnome</c> |
59 |
+and <c>kde</c> flags simply add support for the respective protocols, and do not |
60 |
+depend on external libraries. However, they do increase the Fluxbox binary |
61 |
+size. |
62 |
+</p> |
63 |
+ |
64 |
+<p> |
65 |
+There is also a <c>vim-syntax</c> flag to make configuration easier later on. |
66 |
+This flag will install <c>fluxbox-syntax</c>, a special Fluxbox color scheme for |
67 |
+<c>vim</c>. This enables users to more readily see the contents of their keys |
68 |
+and init files for Fluxbox. It's a tiny extension for vim, so it's highly |
69 |
+recommended. |
70 |
+</p> |
71 |
+ |
72 |
+<p> |
73 |
+Finally, there are two flags that customize the functionality of Fluxbox, |
74 |
+<c>slit</c> and <c>toolbar</c>. These flags are provided so that users who don't |
75 |
+need the <uri |
76 |
+link="http://fluxbox-wiki.org/index.php?title=Faqs#What_is_the_slit">slit</uri> |
77 |
+or the <uri link="http://fluxbox.org/features/">toolbar</uri> can compile |
78 |
+Fluxbox without them. This is useful if you want to run an extremely minimal |
79 |
+environment, or if you plan to use different applications that provide these |
80 |
+features, such as standalone panels or docks. |
81 |
+</p> |
82 |
+ |
83 |
+<p> |
84 |
+Once you've decided on your USE flags, add them to |
85 |
+<path>/etc/portage/package.use</path>: |
86 |
+</p> |
87 |
+ |
88 |
+<pre caption="Example: adding USE flags"> |
89 |
+# <i>echo "x11-wm/fluxbox -gnome -kde truetype vim-syntax" >> /etc/portage/package.use</i> |
90 |
+</pre> |
91 |
+ |
92 |
+<p> |
93 |
It is also necessary to have a program lock the X display to prevent |
94 |
unauthorized access, so it would be wise to also emerge <c>xlockmore</c>. The |
95 |
vast majority of users will also want the ability to set their own background, |
96 |
@@ -102,7 +136,7 @@ |
97 |
</p> |
98 |
|
99 |
<pre caption="Emerging Fluxbox"> |
100 |
-# <i>emerge fluxbox xlockmore x11-terms/eterm</i> |
101 |
+# <i>emerge fluxbox xlockmore eterm</i> |
102 |
</pre> |
103 |
|
104 |
<p> |
105 |
@@ -200,25 +234,6 @@ |
106 |
</body> |
107 |
</section> |
108 |
<section> |
109 |
-<title>Fluxbox Syntax for Vim</title> |
110 |
-<body> |
111 |
- |
112 |
-<p> |
113 |
-Next, install the special Fluxbox color scheme for <c>vim</c>. This enables |
114 |
-users to more readily see the contents of their keys and init files for |
115 |
-Fluxbox. This is a quite small extension for vim, so it is highly recommended |
116 |
-(unless of course you are one of those emacs people, in which case I recommend |
117 |
-<c>emerge -C emacs && emerge gvim</c> ;-). |
118 |
-</p> |
119 |
- |
120 |
-<pre caption="Emerging Fluxbox Syntax"> |
121 |
-# <i>emerge fluxbox-syntax</i> |
122 |
-</pre> |
123 |
- |
124 |
- |
125 |
-</body> |
126 |
-</section> |
127 |
-<section> |
128 |
<title>Application Launcher</title> |
129 |
<body> |