Follow-up Comment #5, bug #65108 (group groff): Your plan looks solid!
I do have one question about two lines at opposite ends of comment #3 that
seem to be in opposition.
> let's rough out a syntax that would work both for existing uses
> of `so` as _soelim_(1) understands it and for formatter syntax,
and
> Since backslash-space is apparently a GNU extension in the
> first place, we might consider dropping it.
So I'm not sure whether or not you advocate retaining soelim's current escape
mechanism. Maybe you're not yet either.
My suggestion in comment #2 that support for soelim's escapes might need to be
dropped was based my concern that one syntax requiring backslashes for spaces
and one not would result in ambiguities in representing edge-case filenames,
such as ones containing a backslash followed by a space. But I think you've
eliminated this possibility by not allowing a bare backslash to represent
itself, requiring it be doubled if the filename contains a backslash. (What
miscreant named this file anyway?)
But if soelim _is_ changed to no longer recognize "\ ", then rule 5a is
unnecessary and even a little counterintuitive.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65108>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
