7 awesomerc - Configuration file for the 'awesome window manager'
11 ..........................
27 ..........................
32 The *awesomerc* file contains configuration informations for *awesome*. It can
33 be used to configure the behaviour and look of awesome in a variety of ways.
35 It is read at startup.
39 *awesomerc* contains 5 global sections: *screen*, *rules*, *keys*, *mouse* and *menu* which
42 All this sections contain options which may be string, integer, float, or even sections again.
44 include::optsdocgen.txt[]
49 In awesome, a lot of *functions* are available. These functions are called
50 uicb (User Interface Call Backs). Each function can be bound to a key shortcut
53 include::uicbdocgen.txt[]
58 More examples are available on awesome's wiki:
59 http://awesome.naquadah.org/wiki/
61 Simple textbox example
62 ~~~~~~~~~~~~~~~~~~~~~~
63 ..............................................
64 1. Add an include directive into ~/.awesomerc
66 screen 0 { include(~/.awesome/bottom-status-bar) }
68 2. Create ~/.awesome/bottom-status-bar
76 3. Check the configuration file for errors
79 Configuration file OK.
81 Note: If you see anything other than "Configuration file OK." you have a
84 4. Create ~/bin/awesome-clock
89 # if you start this from .xinitrc, the script will start before
90 # awesome, and will fail.
91 if [ -S ~/.awesome_ctl.0 ]; then
94 echo "0 widget_tell bottom clock text `date`"
95 echo "" # an empty line flushes data inside awesome
103 Note: What we're saying is "awesome-client, tell the bottom status bar's
104 widget named 'clock' to set it's 'text' property to date's output".
106 5. Make your ~/bin/awesome-clock executable
108 $ chmod a+x ~/bin/awesome-clock
112 ~/bin/awesome-clock &
117 8. If your didn't get what you were expecting, take a look at
118 ~/.xsession-errors or the terminal where X got started.
119 ..............................................
121 Simple progressbar example
122 ~~~~~~~~~~~~~~~~~~~~~~~~~~
123 ..............................................
125 1. Add an include directive into ~/.awesomerc
127 screen 0 { include(~/.awesome/bottom-status-bar) }
129 2. Create ~/.awesome/bottom-status-bar
134 progressbar "diskusage"
138 bordercolor = "#006e96"
141 fg_center = "#daaf0a"
149 3. Check the configuration file for errors
152 Configuration file OK.
154 Note: If you see anything other than "Configuration file OK," you have a
157 4. Create ~/bin/awesome-diskusage
162 # if you start this from .xinitrc, the script will start before
163 # awesome, and will fail.
164 if [ -S ~/.awesome_ctl.0 ]; then
166 usage = `df /dev/sda5 | awk '/\/dev\/sda5/ { print 100-$5 }'`
167 echo "0 widget_tell bottom diskusage data disk ${usage}"
168 echo "" # an empty line flushes data inside awesome
170 done | awesome-client
177 Note: What we're saying is "awesome-client, tell the bottom status bar's
178 widget named 'diskusage' to set it's 'data' property named 'disk' to
181 5. Make ~/bin/awesome-diskusage executable
183 $ chmod a+x ~/bin/awesome-diskusage
187 ~/bin/awesome-diskusage &
192 8. If your didn't get what you were expecting, take a look at
193 ~/.xsession-errors or the terminal where X got started.
194 ..............................................
198 Following skeleton lists all available configuration options in *awesomerc*.
200 ..........................
201 include::rcskeletongen.txt[]
202 ..........................
206 awesome(1) awesome-client(1) awesome-menu(1) awesome-message(1)
210 This man page was written by Julien Danjou <julien@danjou.info>, Marco Candrian <mac@calmar.ws>
211 and Chris Ciulla <chris.ciulla@gmail.com> (Simple Examples).
215 http://awesome.naquadah.org