Private fork of https://github.com/awesomeWM/awesome
1a829fd76d
As discussed on #awesome, the attached patch makes awesome-client exit with a meaningful value (i.e. that of errno) when it encounters an error. Since the most frequent error with awesome-client is a mismatch in the socket path, there is an explicit case for ENOENT errors. I thought of adding a matching fprintf in awesome.c, but you can tell what socket awesome is listening on by looking at what ~/.awesome_ctl.* file you have. CAVEAT: Exiting on error may break setups such as: while true; do echo "some text" done | /path/to/awesome-client which relied on awesome-client continuing to send to the given socket (although failing) until EOF was encountered on stdin. |
||
---|---|---|
layouts | ||
.gitignore | ||
AUTHORS | ||
LICENSE | ||
Makefile | ||
README | ||
STYLE | ||
awesome-client-common.c | ||
awesome-client.c | ||
awesome-client.h | ||
awesome.1 | ||
awesome.c | ||
awesome.doxygen | ||
awesome.h | ||
awesomerc | ||
client.c | ||
client.h | ||
common.h | ||
config.c | ||
config.h | ||
config.mk | ||
draw.c | ||
draw.h | ||
event.c | ||
event.h | ||
layout.c | ||
layout.h | ||
mouse.c | ||
mouse.h | ||
rules.c | ||
rules.h | ||
screen.c | ||
screen.h | ||
statusbar.c | ||
statusbar.h | ||
tag.c | ||
tag.h | ||
uicb.c | ||
uicb.h | ||
util.c | ||
util.h | ||
window.c | ||
window.h |
README
awesome ======= awesome is an extremely fast, small, and dynamic window manager for X. It's based on dwm. Requirements ------------ In order to build awesome you need the Xlib header files, libconfuse and cairo. Installation ------------ Edit config.mk to match your local setup (awesome is installed into the /usr/local namespace by default). Afterwards enter the following command to build and install awesome (if necessary as root): make install Running awesome ----------- Add the following line to your .xinitrc to start awesome using startx or to .xsession to start awesome using gdm/kdm/xdm...: exec awesome In order to connect awesome to a specific display, make sure that the DISPLAY environment variable is set correctly, e.g.: DISPLAY=foo.bar:1 exec awesome (This will start awesome on display :1 of the host foo.bar.) Configuration ------------- The configuration of awesome is done by creating a ~/.awesomerc file. An example is provided in the sources.