X-Git-Url: https://git.cworth.org/git?p=cworth.org;a=blobdiff_plain;f=src%2Fexa%2Fmystery_solved.mdwn;h=7e9744b3ec28f576edc2f5d91f338d02e05d6e87;hp=910b1715410920363d63dba46438620ba9ff1a1c;hb=5c014fe14d7a114dc525711d3236feb10f27177f;hpb=b96048fb57858c3c9323e20e86ce6a36a69fef73

diff --git a/src/exa/mystery_solved.mdwn b/src/exa/mystery_solved.mdwn
index 910b171..7e9744b 100644
--- a/src/exa/mystery_solved.mdwn
+++ b/src/exa/mystery_solved.mdwn
@@ -1,22 +1,22 @@
-[[meta title="Rectangles mystery solved"]]
+[[!meta title="Rectangles mystery solved"]]
 
-[[tag exa performance xorg]]
+[[!tag exa performance xorg]]
 
-So I found the answer to my [[fill rate
+So I found the answer to my [[!fill rate
 confusion|corrected_rectangles]] and it turned out to not be all that
 interesting in the end---no pretty graphs this time. And it should
 have been obvious to me---though admittedly the EXA run time was too
 fast for me to _see_ what was happening.
 
 What I did was eliminate all the variables of the cairo-perf test
-suite by writing a tiny [[standalone test case|rectangles.c]].  I
+suite by writing a tiny [[!standalone test case|rectangles.c]].  I
 happened to be running an XAA server at the time, and when I ran the
 test it gave exactly the same results as `x11perf -rect500`. They both
 rendered 501 500x500 rectangles per second. But there was an obvious
 difference, x11perf flashed wildly while my test stayed a constant
 black.
 
-So a quick glance with xtrace---by the way this is the long [[sought
+So a quick glance with xtrace---by the way this is the long [[!sought
 after|understanding_rectangles]] X protocol tracer that actually
 decodes Render requests, and it's much easier to use than any of xmon,
 xscope, or wireshark. Hurrah! (And many thanks to Behdad for pointing