On Tue, Jul 14, 2009 at 03:23:09PM +0200, Nido wrote: > According to the xclock man page, under options, at '-render', it > claims using Xrender is default when xclock is compiled with Xrender > support. > > However; running xclock without arguments looks the same as when ran > with the -norender option. Running xclock with the -render gives > smooth clock hands, so it seems reasonable to me to assume Xrender > support is built in and works. > > This is tested on my laptop with a -current snapshot from 07/07. The > video card is an Intel GM965 builtin (8086 2a03).
You are correct. However, xclock is part of the X.org project and thus it would be best if you could report this bug upstream at http://bugs.freedesktop.org. alternatively, the following diff should make the manpage true: Cheers, -0- -- I used to be an agnostic, but now I'm not so sure. Index: Clock.c =================================================================== RCS file: /cvs/xenocara/app/xclock/Clock.c,v retrieving revision 1.4 diff -u -p -r1.4 Clock.c --- Clock.c 27 Nov 2007 11:30:33 -0000 1.4 +++ Clock.c 14 Jul 2009 13:58:16 -0000 @@ -189,7 +189,7 @@ static XtResource resources[] = { offset (backing_store), XtRString, "default"}, #ifdef XRENDER {XtNrender, XtCBoolean, XtRBoolean, sizeof(Boolean), - offset(render), XtRImmediate, (XtPointer) FALSE }, + offset(render), XtRImmediate, (XtPointer) TRUE }, {XtNbuffer, XtCBoolean, XtRBoolean, sizeof(Boolean), offset(buffer), XtRImmediate, (XtPointer) TRUE }, {XtNsharp, XtCBoolean, XtRBoolean, sizeof(Boolean),
