@DavidCarlisle In one of the mails: the key is not the code itself but the fact that there are a lot of files. Saying it needs a current LaTeX is a stretch - there are a lot of modifications.
@JosephWright anyway I was going to suggest that we say for this time round that (apart from existing use in hyphenation files) we would leave the error message but not make much use of etex, so their ini file can use \let\eTeXversion\relax to get past the error and then it's up to them to fake whatever is needed, perhaps by copying from an old latex.ltx. But it's a flag that future edits may start using etex more
@DavidCarlisle I thought about, but we are not talking about a change that can readily be backed-out or one that will affect how documents look (my understanding is that includeinrelease is meant to cover those cases)
@DavidCarlisle Won't really work anyway as you can't build the format without eTeX if you check for it at the start
@JosephWright yes I know, maybe just consider it an "engine change" (addresed 30 years late) anyway since using etex and removing tex2 support is supposed to simplify the code base, then that aim certainly won't be met if every use of etex stuff has to have the docstrip guards for latexrelease
@yo' official answer is that list parameters are the only interface to parskip, but you can always do something, don't know exam sheet well enough without an example to suggest what..
@yo' The most important aspect of \list is that it sets \parshape \@ne \@totalleftmargin \linewidth and works very hard in continuing with this setting when a paragraph ends.
@JosephWright if @egreg comes next year could UKTUG push the expenditure to include groceries.iceland.co.uk/… it's "italian" so should make him feel at home.
@JosephWright hah. To be fair, I recently discovered a bug in a package that @DavidCarlisle is in charge of.
Ok, so I've surveyed my lab mates, so far all the native Canadians I've asked, but one spell them meter & litre. The one who spelled it liter said use used to use litre, but switched after reading a ton of scientific papers.
@Canageek yes found the discussion, firstly it's not my code, I literally inherited it after Sebastian died, and I mentioned the possibility of a bug before I had seen what it was doing, which is using lrbox, so it comes down to user error not a bug, sorry:-)
@Canageek in 1993 frank and I spent weeks going through the sources and removing redundant {} and space tokens we saved several hundred bytes and you ask why it doesn't save arbitrary chunks of text just in case:-)
@egreg some talk I heard recently about different people having different ideas about signs and words like BUG (or DOG). Forgotten all the details by now of course!
@Canageek I prefer the tex definition, something which even by taking the most strained and forced interpretation of the texbook you can not avoid the conclusion that the book explicitly says that it will not happen.
@PauloCereda I don't know why I bother to ask, but why did you post that? Just to split up Ulrike's and Johannes' conversation with some more authentic German?
