On Mon Feb 24, 2025 at 2:36 AM CET, G. Branden Robinson wrote: > [...] > My lodestar on this point is that we can use C and the shell to create > files named with trailing spaces, so there's no reason *roff, as a bona > fide programming language, shouldn't be capable as well--as long as it's > not difficult to implement. > > Further, because such file names _are_ so easy to create in C and the > shell, I think if there were dangerously underhanded threats in the > offing, we'd have seen them by now. It's not like people need to > smuggle such things onto the file system under the cover of a *roff > document. (In GNU troff, since "safer mode" is on by default, a > document can't _create_ a file of _any_ name on its own initiative.)
I think the point is that such filenames aren't being used, so breaking compatibility (and making adding comments to these requests annoying) for the sake of supporting them isn't worth it. ~ onf
