search for: verically

I've heard this second hand and haven't had the time to confirm its vericity. Can someone confirm this is the case? If so, what were these people thinking? Removing support for the only video format that is sure to be installed in every Linux box somehow promoves the OS adoption? You get a WTF award LF, congrats. -Ivo

Funnily enough, it seems that adjustment of text in the verical direction is more flexible than in the horizontal. Horizontal adjustment parameters, seem to be set to the closest of 0 and 1 if they fall outside (0,1). Try e.g.: plot(0:1,0:1) for (a in seq(-5,5,0.5) ) text(0.5, 0.5, "Y", adj=c(0,a), cex=2, col="red" ) for (a in seq(-5,5,0.5) ) text(0.5, 0.5, "X",

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The list server at shorewall.net is seeing a small but steady stream of quaranteened messages from anti-spam software that is asking the list server to respond and thus register itself as a legitimate source of email. I also receive these requests personally. Here''s an example: -

Hi all, I'm sure this is reallly basic, but I just can get it to work. I want to plot six box & whisker plots together to make one figure so that they appear one below the next. I can do this using >par(mfrow=c(6,1)), but each box&whisker plots end up vertically compressed to the point where I can't see the actual bars, and there is a large amount of white space between each

Hi all, with PowerPoint and ThinkCell one can draw something they call waterfall chart and it looks like this: http://www.think-cell.com/products/images/waterfall.gif I found discussions on waterfall charts in the archive of this mailinglist, but unfortunately they looked totally different. Other names for this type of plot seem to be bridge chart, cascade chart, stair case chart, etc. but

Hi, Here I post these 2 misc patches. Best regards, Maxim Levitsky

Hi, Here is my patch queue I accumulated over quite a long time. Patches 1-6 are bugfixes, and rest is mostly RFC. Comments are welcome. Best regards, Maxim Levitsky

The current code for primitive splitting and emission on pre-nv50 is severely broken. In particular: 1. Quads and lines are totally broken because "&= 3" should be "&= ~3" and similar for lines 2. Triangle fans and polygons are broken because the first vertex must be repeated for each split chunk 3. Line loops are broken because the must be converted to a line strip,