Hi onf,
At 2024-12-02T02:14:56+0100, onf wrote:
> No changes to groff are, strictly speaking, necessary.
> Your planned changes to .ad aren't necessary by the same logic either.
> But you desire them anyway because they make groff's behavior more
> reasonable. The same desire has motivated my prop
Hi onf,
At 2024-12-02T02:26:12+0100, onf wrote:
> D'oh. I am sure I confused you even more. I meant to say either: To
> summarize, `ne` would break line if not in compatibility mode and
> called with the regular control character.
>
> ... or ...
> To summarize, `ne` would NOT break line if
>
[please reply to the groff@ as well; I am not subscribed to autoconf@]
Apparently I am having a moment of dumb.
In preparation for a 1.24 release, I am trying to get groff building on
Solaris 10, which has yet again received a stay of execution from
Oracle.[1]
https://blogs.oracle.com/solaris/po
Hi Branden,
Do you intend to fix this? Should I report a bug in Savannah?
Cheers,
Alex
On Mon, Nov 25, 2024 at 12:36:49AM +0100, Alejandro Colomar wrote:
> On Sun, Nov 24, 2024 at 11:43:57PM +0100, onf wrote:
> > On Sun Nov 24, 2024 at 10:52 PM CET, Alejandro Colomar wrote:
> > > I'm having a b
Hi Alex,
At 2024-12-01T15:17:22+0100, Alejandro Colomar wrote:
> I was wondering if it would be good to nest SY/YS.
>
> What do you think of this?:
>
> .SY void\~*bsearch (
> .BI const\~void\~ key [. size ],
> .BI const\~void\~ base [. size \~*\~. n ],
> .BI size_t\~ n ,
> .BI size_t\~ size
> I get an error "sh: line 1: missing: command not found"
> And then:
> Calling 'echo showpage | missing -q -dBATCH -dSAFER -dDEVICEHEIGHTPOINTS=792
> -dDEVICEWIDTHPOINTS=700 -dFIXEDMEDIA=true -sDEVICE=pnmraw -r100
> -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -sOutputFile=/tmp/groff-page-p9UCo9
Hi all,
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. This issue has been
discussed extensivel
On Mon Dec 2, 2024 at 2:14 AM CET, onf wrote:
> To summarize, `ne` would break line if
> a) in compatibility mode
> b) not in compatibility mode and called with the regular control
> character
D'oh. I am sure I confused you even more. I meant to say either:
To summarize, `ne` would brea
Hi Branden,
On Mon Dec 2, 2024 at 12:51 AM CET, G. Branden Robinson wrote:
> At 2024-12-01T23:06:41+0100, onf wrote:
> > I propose the following changes to make their behavior consistent:
> >
> > 1. `ne` breaks line before breaking the page as `bp` does
> > 2. `ne` does not break line before br
At 2024-12-01T22:17:47-0600, Dave Kemper wrote:
> On Sun, Dec 1, 2024 at 8:27 PM G. Branden Robinson
> wrote:
> > By contrast, your sample size for `ne` misuse is one--yourself.
> > Formerly two, before I came to understand the request.
>
> Well, I agree with onf's point that .ne's behavior defie
On Sun, Dec 1, 2024 at 8:27 PM G. Branden Robinson
wrote:
> By contrast, your sample size for `ne` misuse is one--yourself.
> Formerly two, before I came to understand the request.
Well, I agree with onf's point that .ne's behavior defies user
expectation, so you can lump me in with that sample.
Hi onf,
At 2024-12-02T04:45:27+0100, onf wrote:
> On Mon Dec 2, 2024 at 3:26 AM CET, G. Branden Robinson wrote:
> > > One two three
> > > four five six
> > > 'bp
> > > seven eight nine
[...]
> > > It's obvious here that 'bp breaks page IMMEDIATELY, not when the
> > > .br
> >
> > Eh?
> >
>
At 2024-12-02T05:15:36+0100, onf wrote:
> page break = end line, end page
[...]
> page break = end page
>
> Please correct me if I'm wrong.
I don't think we're to the point yet where I can say you're right or
wrong.
> Consulting the web, a 'page break' is variously defined as one of:
> start o
On Mon Dec 2, 2024 at 5:54 AM CET, G. Branden Robinson wrote:
> At 2024-12-01T22:17:47-0600, Dave Kemper wrote:
> > On Sun, Dec 1, 2024 at 8:27 PM G. Branden Robinson
> > wrote:
> > > By contrast, your sample size for `ne` misuse is one--yourself.
> > > Formerly two, before I came to understand th
On 12/1/24 21:03, 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.
First question: what shell is configure actually running under?
Autoconf makes an effort to find a plausible POSIX shel
On Mon Dec 2, 2024 at 3:26 AM CET, G. Branden Robinson wrote:
> [...]
> > $ nroff << EOF | sed -E 's/^/./'
> > .pl 3
> > .fi
> > One two three
> > four five six
> > 'bp
> > seven eight nine
> > .br
> > eleven twelve.
> > EOF
> > output:
> > .
> > .
> > .
> > .One two thr
Reading your message for at least the third time, I conclude that:
On Mon Dec 2, 2024 at 3:26 AM CET, G. Branden Robinson wrote:
> [...]
> > $ nroff << EOF | sed -E 's/^/./'
> > .pl 3
> > .fi
> > One two three
> > four five six
> > 'bp
> > seven eight nine
> > .br
> > eleven twel
Hi Branden,
On Mon Dec 2, 2024 at 5:27 AM CET, G. Branden Robinson wrote:
> At 2024-12-02T04:45:27+0100, onf wrote:
> > We seem to interpret the word 'page break' differently. I interpret
> > it the way it's used in the groff manpage, that is, as a way of saying
> > "end the page and start a new
Hi Jacob,
Thanks for the quick response.
At 2024-12-01T23:48:09-0600, Jacob Bachmeyer wrote:
> On 12/1/24 21:03, 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.
>
> First q
Hi Branden,
I was wondering if it would be good to nest SY/YS.
What do you think of this?:
.SY void\~*bsearch (
.BI const\~void\~ key [. size ],
.BI const\~void\~ base [. size \~*\~. n ],
.BI size_t\~ n ,
.BI size_t\~ size ,
.br
-.BI int\~(* compar )(const\~void\~[. size ],
+.SY int\~(*\f[
Hi onf,
At 2024-12-01T23:06:41+0100, onf 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 reasonably
21 matches
Mail list logo
