21:21:45jackdanielInline: thank you. I've reviewed your PR – you need to clean it up from unnecessary changes, fix indentation and split separate changes into commits with commit messages which describe why the change was made (what was wrong and how it addresses the issue)
21:22:04jackdanielplease also write down steps how to reproduce the issue
22:19:13jackdanielas of number of lines, to day for instance I have changes which count around 250 lines, but it is a very poor way of measuring things
5:05:24lokeI have only two plans for the weekend: 1) To visit the science museum, and 2) To go to a specialised beer shop and buy some local beers to bring back home
5:06:18beachI was hoping you could come to Bordeaux on Saturday, we have dinner, you stay over night and go back on Sunday. But that won't work, will it?
5:06:43lokeWell. I have considered Bordeaux, but I'd go on sunday morning and go back in the evening
6:10:17lokeIf you want to try the latest version, it's available in the usual place. It now has documentation :-)
6:10:58lokeI've also fixed a million documentation errors in Maxima itself. They god annoyed with my posting patches so I have commit rights there now. :-)
6:11:11beachOK. Today I am a bit busy. My favorite coauthor is coming over for lunch. Our normal schedule is on again after the holidays. So I have to work on our papers, fix lunch, clean up, work again.
6:20:29beachloke: When you know your time of arrival, please let me know. Also if you have a phone number that works in France, it might be good to give it to me, say by email. And you should let me know if you have any food restrictions.
6:21:28beachloke: Oh and the car number you are in. I'll be on the platform waiting for you.
7:34:11jackdanielloke: yes, but I don't mention it because it was usually erroneous
7:34:41jackdanielmost time "stupid restrictions" have a reson to (even if I don't know why they are there)
8:26:39scymtymthe most satisfying thing is fixing a long-standing problem in some part of the code and then removing a stupid restriction elsewhere that was necessary because of the problem
9:02:17jackdanielright now when we record stream text output records we always close them when newline occurs. that applies to both user newlines and wrapping newlines (put there by us)
9:02:32jackdanielas a consequence no text output record spans more than one line
9:03:11jackdanielI wonder how feasible would it be to subsume soft newlines into open text output records as well (so one record may span multiple lines)
9:03:32scymtymjackdaniel: thanks for the baseline fix. my trace recorder started looking better over night
9:04:11jackdanielI have more changes, but I didn't want to put too much into single PR (pattern PR was way too big for instance)
9:05:04jackdanieland regarding yesterday's question: I've decided on :wrap* for end-of-line-action when we want to wrap by word
9:05:44jackdanielmaybe a bit cryptic, but easy to remember when you know about it
9:06:28jackdanielbecause it is harder to remember - "which one was that - wrap-word or word-wrap?" and also to maintain convention when I've introduced :baseline* (and not :last-line-baseline)
9:06:40jackdanielit is a variant of wrapping like baseline* is a variant of baseline alignment
9:07:18scymtymok. i don't feel strongly about this