13:11:08beachI sometimes use a smaller typeface for code, so as to avoid too long lines. Code is not as hard to read when it is small, due to the fixed font.
13:13:28scymtym_true, the pdf version would benefit from a smaller font size in listings. but it is hard to make all output formats (pdf, info, html) look good simultaneously
13:18:26beachAnd the text font is more readable too.
13:37:19scymtym_jackdaniel: i think the undefined function in the test execution failure i described is COORDINATE-IN*
13:39:58jackdanielscymtym_: it seems I've pushed my wip changes, sorry. looking into that now
13:42:00jackdanielyes, commit "geometry: region predicates: sort out ...", I thought I have it stashed not commited
13:43:00jackdanielscymtym_: I've removed the offending commit
14:15:28jackdanielscymtym_: it is put in a single and for a reason: you don't want to have four reports when the issue is with rounding (in case of ellipses it is indeed rounding issue, i.e 14.99999 vs 15 -- their representation is suboptimal). I think that a helper function will be better indeed.
14:18:09scymtym_i would want four reports with offending values instead of just NIL, but that may be personal preference
14:18:31scymtym_putting the whole pattern into a helper function will make changes easy in any case
14:27:54scymtym_jackdaniel: how do you want to deal with the failing tests?
14:28:57jackdanielI want to change the representation
14:29:40scymtym_will the change be part of the pull request?
14:29:58jackdanielno, this is a long standing issue and it will be part of the next pull request
14:30:57jackdanielfirst canonicalize radii to orthogonal vectors and represent elliptical thing as vectors aligned with xy + ellipse rotation. I haven't tried it yet, but I have hopes that it will give more accurate results and will be easier to work with
14:31:18jackdanielfor point belonging we can always transform the ellipse to polar coordinates (or even retain such transformation)