On Sun, Feb 2, 2025 at 3:18 PM Hans Hagen
well, 1.10 was kind of an official release where we decided that this-is-it also because of pressure to freeze (before that we only had sort of stable development snapshots for TL) but realy freezing happened bit later with it now being deep-freeze
Oh, I see. Thanks for the clarification.
because displaymmath is used in various scenarios: as a pargaraph of its own, inside a paragraph (where it is assumed to take 3 lines), in order to catch a previous line width (kind of an abuse), etc
we also don't remove dir nodes from hboxes when there's only dirs (so \ifvoid is seeing them)
Interesting, I've never thought about it.
indeed something like that has to be under mode primitive control; for an empty paragraph one can argue that the textdir is a side effect but for a construct like display math it's a bit different, so maybe mode control is indeed needed here (\mathemptydisplaymode) as we can't know if it won't break something where it is assumed
so can you add a mode ? (i have no time for doing that now)
Absolutely! Any preferences on what values should it take? Positive/Negative like \matheqdirmode or simply 1 like \breakafterdirmode? Another option, to avoid introducing a new primitive, is that if \mathdisplayskipmode is negative (-1, -2 or -3) then null pars will be flushed (kind of make sense as it also controls white space), and for the skip around the display the absolute value will be taken into account. Udi