On 2026-11-04 12:07, Jon Forrest wrote: > On Page 12, section 3.1.1 is the paragraph > > "Outside of recipe lines, backslash/newlines are converted into a single > space character. Once that is done, all whitespace around the backslash/ > newline is condensed into a single space: this includes all whitespace > preceding the backslash, all whitespace at the beginning > of the line after the backslash/newline, and any consecutive backslash > newline combinations."
It doesn't seem that this could be misinterpreted or cause puzzlement. Of course "preceding the backslash" means "preceding the space representing the removed backslash" and not "preceding the backslash in its new home location in the bit bucket to which it has been removed". :) > My minor nit is that this is describing two events, but the second > event can't happen because the first event already converted > the backslash/newlines into whitespace. So, there's no backslash/newline > around which whitespace can be condensed. > > I think this paragraph would be clearer if it were reworded as follows: > > "Outside of recipe lines, backslash/newlines are converted into a single > space character. Once that is done, all whitespace before where the > backslash/newline used to be is removed, leaving only the newly created space > character. This includes all leading whitespace at the beginning > of the next line and any consecutive lines ending with a backslash/newline > combination." This seems logically equivalent to replacing all sequences which match the regex (\s*(\\\n)+\s*)+ with a single space. In other words, maybe the requirement can be stated as: every character sequence which consists of any mixture of zero or more whitespace characters, and at least one backslash-newline digraph, is replaced by a single space.
