@kan According to en.wikipedia.org/wiki/Maggi "In India, Maggi instant noodles are a favorite for an anytime meal. From dorm rooms of colleges to late-night cooking in home kitchens, it's an all-time favorite."
For something completely different, Dortmund (late national champion) is playing against Munich (record national champion) tomorrow. After having been outstanding in champions league and mediocre in national league, there is a lot of suspense how Dortmund will perform...
@PauloCereda Going to the stadium is not really my cup of tea, though my father and my daughter (and a lot of colleagues) love it. I've never been in Westfalenstadion ;-)
@egreg Have you come across this kind of "normalisation"? A vector in ℚ^4, for eg, (0, 2, 3, 4) being "normalised" to: (0, 1, 3/2, 2)... that is, the vector, being divided by its first non-zero component.
Well, time is definitely a parameter, but only one of the several parameters. For instance, I believe in looking for opportunities where you can write some code...
@PeterGrill I don't care much about the arrows, but I'm wondering if there's a less kludgy way to have the arrow from T to C avoid the VP structure? (Other than adding the temp node manually.)
@PeterGrill No, I realize that, but what I'm asking you has nothing to do with tikz-qtree but with tikz more generally. So is there any way to specify a way to draw between two nodes and avoid some other part of the drawing?
Almost every article I've read 1 comparing Git and Mercurial it seems like Mercurial has a better command line UX with each command being limited to one idea only (unlike say git checkout).
But at some point Git suddenly became looking super popular and number of Git submitters on Debian popcorn...
@TorbjørnT. :) It's always fun to see your own questions quoted at you! Thanks, Torbjørn, I'd forgotten about that one.
@PeterGrill Cool. That works really nicely. It's not really a general solution since it's only an accident that the structure to be avoided is at the bottom of the whole picture. I'll add a comment about doing it that way in this particular case, but the tmp node solution for the moment is more adaptable to other situations.
@AlanMunn Not sure if there is an easy general solution. I guess you could use the fit library to define new nodes that you want want to avoid and go around then. But that still requires a temp node to be created.
@percusse Perfect. I like that solution best of all. It's much more general, and it allows you to avoid the structure in a way that is sensible with respect to the tree nodes themselves. I'll update the answer.