It also fails with the gb4e and linguex examples. So this is something quite general with lists.
–
Alan MunnMar 15 '11 at 2:06

6

This question has been upvoted enough times that it looks like it deserves an answer, so I've offered a bounty on it. Most upvoted answer this time next week gets it.
–
SeamusMar 21 '11 at 15:05

@Seamus Thanks for adding the bounty to this question -- it looks like it was just what was needed to smoke out the answer. As far as I understand, if I accept Ulrich's answer, he will get the bounty. You mentioned waiting a week, but consensus seems to be that his answer is deserving. Any objections if I go ahead and accept it?
–
AaronMar 23 '11 at 18:56

I'm not sure whether accepting the answer will trigger the bounty, since it wasn't offered by the asker. But I'm perfectly happy for Ulrich to get the bounty so go ahead and accept!
–
SeamusMar 23 '11 at 19:01

\@result is the problem but not in TikZ but in tikz-qtree and in cleveref
–
Alain MatthesMar 21 '11 at 19:17

Sadly, grep -rl '\\@result' reveals nothing in the PGF directories (and all the results of grep -r @result are normal so there's no apparent \csname trickery). Though not knowing much of the mysteries of TeX, could it be encoded in some weird way?
–
Loop SpaceMar 21 '11 at 19:22

1

Ah, yes. As Altermundus says, line 30 of tikz-qtree.sty reads \newtoks\@result. That should be easy to patch. I guess that both packages should choose better names!
–
Loop SpaceMar 21 '11 at 19:24

2

Ulrich should get the bounty. I'm annoyed that I missed this when I looked into this last week! Changing all instances of \@result to \tkqt@result fixes the problem. I'm in contact with the author of tikz-qtree, so I'll send a fix along to him.
–
Alan MunnMar 21 '11 at 19:25