Presuming we are running awesome on this screen, and this is
screen 0,
* we replace the running awesome instance by a freshly compiled
one with the "restart-uninstalled" target,
* we replace the running awesome instance by the last installed
one with the "restart-installed" target.
Note this can render your running X11 screen unusable.
A little bit of test magic starting Xnest should make more
confined tests possible with less serious failure modes.
Signed-off-by: Julien Danjou <julien@danjou.info>
If xmlto is present, create a very simple example man page by
running 'xmlto man'. Only generate man pages at "make all" time
if this works.
The check is a little lenthy, so we might want to put it into
a separate .m4 file some time.
Signed-off-by: Julien Danjou <julien@danjou.info>
At every build ("make", "make all"), if necessary, this
version message will be updated.
Note that "make awesome{,-client}" will NOT update the
version message.
Signed-off-by: Julien Danjou <julien@danjou.info>
Updates awesome-version.h every time the version number has
actually changed. The normal C header deps will then trigger
the appropriate rebuilds.
Signed-off-by: Julien Danjou <julien@danjou.info>
I missed this feature for some time too, then I've just added two
layouts with master and stack area separated horizontaly: tiledown and
tileup (with the stack area down and up respectively) by adding a third
argument telling whether one wants to separate horizontally or verticaly
to the _tile function in layouts/tile.c. Patch against latest git
version, you will need to have icons
icons/layouts/{tiledown.png,tiledownw.png,tileup.png,tileupw.png} to
compile it without modifications.
Fabienne
Signed-off-by: Julien Danjou <julien@danjou.info>
Use a single script to generate the version number from git. This script
* strips the v from the start of the "git describe" output
* changes all "-" occurences to "."
* does NOT create a properly sortable version number from "2.1-rc2"
type "git describe" output
* does NOT generate a "proper" "1.2.3" type version number under any
circumstances
* will generate "2.1" in case the "git describe" output is "2.1"
These policy might need closer adaption to awesome's tagging habit
some time.
In dist tarballs, ship a "version-stamp" file with the package version
in it. If the "version-stamp" file is present (i.e. if it is a source
tree from a dist tarball), no git checks will be performed.
Concept from autoconf, but code written from scratch to match
awesome's requirements.
Signed-off-by: Julien Danjou <julien@danjou.info>
example config:
graph gr_cpu {
width = 80
height = "0.8"
fg = "#336633"
bg = "#000000"
bordercolor = "#669966"
padding_left = 0
mouse = {...}
x = ...
y = ...
}
Looks like here: http://www.calmar.ws/tmp/112-Sun-screen.png
I renamed lpadding to padding_left, and bcolor to bordercolor
also on the progressbar widget.
The awesomerc page would still be to write, when this patch will get accepted.
Hints are always welcomed.
Hans Ulrich Niedermann
Julien Danjou
Fabienne Ducroquet
marco candrian
