Re: Differences in `ne` and `bp` line-breaking behavior

2024-12-02 Thread Douglas McIlroy
Re: Differences in `ne` and `bp` line-breaking behavior > I have discovered recently that `ne` and `bp` behave differently in > regards to pending input lines. `bp` breaks such lines, while `ne` > does not. In practice this means that `ne` does not behave like a > conditional `bp` as one would re

Re: stumped on a simple autoconf/m4/sh problem

2024-12-02 Thread Paul Eggert
On 2024-12-01 19:03, G. Branden Robinson wrote: The problem is that the test exercising `$cmd` succeeds on Solaris 10 when it should not. Why shouldn't the test succeed? Solaris 10 /usr/bin/tr supports character classes like [:cntrl:].

Re: Differences in `ne` and `bp` line-breaking behavior

2024-12-02 Thread Deri
On Sunday, 1 December 2024 23:51:22 GMT G. Branden Robinson wrote: > I don't agree with this change, because it's not necessary. Formatter > requests are primitive things. Most requests don't also perform breaks. > Only a handful do. Those that do support the no-break control character > to _sch

Re: Differences in `ne` and `bp` line-breaking behavior

2024-12-02 Thread onf
On Mon Dec 2, 2024 at 7:19 PM CET, Tadziu Hoffmann wrote: > > > I have discovered recently that `ne` and `bp` behave differently in > > > regards to pending input lines. `bp` breaks such lines, while `ne` > > > does not. In practice this means that `ne` does not behave like a > > > conditional `bp`

Re: stumped on a simple autoconf/m4/sh problem

2024-12-02 Thread G. Branden Robinson
At 2024-12-02T12:55:02-0800, Paul Eggert wrote: > On 2024-12-02 12:26, G. Branden Robinson wrote: > > > Why shouldn't the test succeed? Solaris 10 /usr/bin/tr supports > > > character classes like [:cntrl:]. > > It doesn't for me in the instance at gcc210.fsffrance.org. > > It works for me there:

Re: Differences in `ne` and `bp` line-breaking behavior

2024-12-02 Thread onf
Hi Branden, On Mon Dec 2, 2024 at 9:56 PM CET, G. Branden Robinson wrote: > I therefore think our description of `ne` in groff(7) pretty badly needs > revision. > > Here's what it says now. > >.ne Break page if distance to next page location trap is > less than one v

Re: stumped on a simple autoconf/m4/sh problem

2024-12-02 Thread Paul Eggert
On 2024-12-02 12:26, G. Branden Robinson wrote: Why shouldn't the test succeed? Solaris 10 /usr/bin/tr supports character classes like [:cntrl:]. It doesn't for me in the instance at gcc210.fsffrance.org. It works for me there: $ uname -a SunOS gcc-solaris10 5.10 Generic_Virtual sun4u spa

Re: stumped on a simple autoconf/m4/sh problem

2024-12-02 Thread G. Branden Robinson
Hi Paul, At 2024-12-02T11:45:30-0800, Paul Eggert wrote: > On 2024-12-01 19:03, G. Branden Robinson wrote: > > The problem is that the test exercising `$cmd` succeeds on Solaris > > 10 when it should not. > > Why shouldn't the test succeed? Solaris 10 /usr/bin/tr supports > character classes like

Re: Differences in `ne` and `bp` line-breaking behavior

2024-12-02 Thread G. Branden Robinson
At 2024-12-02T13:05:50-0500, Douglas McIlroy wrote: > > I have discovered recently that `ne` and `bp` behave differently in > > regards to pending input lines. `bp` breaks such lines, while `ne` > > does not. In practice this means that `ne` does not behave like a > > conditional `bp` as one would

Re: Differences in `ne` and `bp` line-breaking behavior

2024-12-02 Thread onf
On Mon Dec 2, 2024 at 7:05 PM CET, Douglas McIlroy wrote: > > I have discovered recently that `ne` and `bp` behave differently in > > regards to pending input lines. `bp` breaks such lines, while `ne` > > does not. In practice this means that `ne` does not behave like a > > conditional `bp` as one

Re: Differences in `ne` and `bp` line-breaking behavior

2024-12-02 Thread Tadziu Hoffmann
> > I have discovered recently that `ne` and `bp` behave differently in > > regards to pending input lines. `bp` breaks such lines, while `ne` > > does not. In practice this means that `ne` does not behave like a > > conditional `bp` as one would reasonably expect. > > I invented .ne 55 years ag

Re: Differences in `ne` and `bp` line-breaking behavior

2024-12-02 Thread Tadziu Hoffmann
>.ne Advance drawing position to the next vertical position > trap if it is nearer than one vee. >.ne d Advance drawing position to the next vertical position > trap if it is nearer than distance d (default scaling > uni

Re: stumped on a simple autoconf/m4/sh problem

2024-12-02 Thread Jacob Bachmeyer
On 12/2/24 00:47, G. Branden Robinson wrote: Hi Jacob, Thanks for the quick response. I happen to be up late here. At 2024-12-01T23:48:09-0600, Jacob Bachmeyer wrote: On 12/1/24 21:03, G. Branden Robinson wrote: [...] [...] Okay, I did. The mystery would appear to deepen. The same grep g

Re: stumped on a simple autoconf/m4/sh problem

2024-12-02 Thread Zack Weinberg
On Sun, Dec 1, 2024, at 10:03 PM, G. Branden Robinson wrote: [...] > So the "good tr" branch is being taken in the configure script, but > not in vivo at a shell prompt. I can't explain this. I have no immediate explanation either. On the Solaris 10 machine from the GCC compile farm, I'm seeing

Re: Differences in `ne` and `bp` line-breaking behavior

2024-12-02 Thread G. Branden Robinson
Hi Tadziu, At 2024-12-03T00:22:40+0100, Tadziu Hoffmann wrote: > >.ne Advance drawing position to the next vertical position > > trap if it is nearer than one vee. > >.ne d Advance drawing position to the next vertical position > > trap i