Re: spaces in file names and before comments

2025-02-24 Thread onf
On Mon Feb 24, 2025 at 3:52 AM CET, G. Branden Robinson wrote: > At 2025-02-24T03:36:28+0100, onf wrote: > > 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

Re: spaces in file names and before comments

2025-02-24 Thread G. Branden Robinson
At 2025-02-23T23:34:36-0600, Dave Kemper wrote: > On Sun, Feb 23, 2025 at 8:52 PM G. Branden Robinson > wrote: > > At 2025-02-24T03:36:28+0100, onf wrote: > > > I think the point is that such filenames aren't being used, > > > > No, that's not "the point". It's _your_ point, > > Hey, originally

Re: spaces in file names and before comments

2025-02-23 Thread Dave Kemper
On Sun, Feb 23, 2025 at 8:52 PM G. Branden Robinson wrote: > At 2025-02-24T03:36:28+0100, onf wrote: > > I think the point is that such filenames aren't being used, > > No, that's not "the point". It's _your_ point, Hey, originally it was *my* point :-P > > so breaking compatibility (and making

Re: spaces in file names and before comments

2025-02-23 Thread G. Branden Robinson
At 2025-02-24T03:36:28+0100, onf wrote: > 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, sh

Re: spaces in file names and before comments

2025-02-23 Thread onf
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

spaces in file names and before comments (was: double quotes in file names: another groff 1.24.0 caveat)

2025-02-23 Thread G. Branden Robinson
[re-titling sub-thread again] At 2025-02-22T17:59:10-0600, Dave Kemper wrote: > I still suspect that that benefit stands even if the file-opening > function is modified to chop trailing spaces from the name. That > would prevent groff from opening a file named "trailing space ", but > any real-wo

Re: spaces in file names and before comments

2025-02-22 Thread onf
By the way, On Sun Feb 23, 2025 at 12:53 AM CET, G. Branden Robinson wrote: > At 2025-02-22T23:23:35+0100, onf wrote: > > If that's an accurate characterization, then please explain what that > > NEWS file is about, because I don't get it. > > Again your references are too broad and too general.

Re: spaces in file names and before comments

2025-02-22 Thread onf
Dear Branden, On Sun Feb 23, 2025 at 12:53 AM CET, G. Branden Robinson wrote: > [...] > > It doesn't, because there is not a single line containing a comment > > separated from the argument by a space. Read the examples I gave > > above. > > I understand now. You are bewailing the removal of supp

spaces in file names and before comments (was: double quotes in file names: another groff 1.24.0 caveat)

2025-02-22 Thread G. Branden Robinson
[giving this sub-thread a more appropriate title] At 2025-02-22T23:23:35+0100, onf wrote: > [re-arranging] > > On Sat Feb 22, 2025 at 9:37 PM CET, G. Branden Robinson wrote: > > At 2025-02-22T16:38:00+0100, onf wrote: > > [...] > > > I feel like changing ab, hpf, hpfa, nx, so, and tm (the others