Ralf Wildenhues <[EMAIL PROTECTED]> writes: > but I wouldn't know how to make it foolproof. First, if the space is > missing after `>' and $file begins with `>', then append mode is used. > But also, if $file begins with whitespace, that is just ignored anyway.
I'm a bit out of context here, but can't you prepend "./" to the file name, if the file begins with " " or ">" or any other troublesome character? > - If the build tree name contains whitespace, the manpages come out > wrongly. The synopsis says > | dir with spaces/build/bin/ifnames [OPTION] ... [FILE] ... I assume that's a bug already, right? If so, it doesn't hurt to put the fix off until later. Thanks for taking this on.
