Re: .ab oddity

2023-02-05 Thread John Gardner
> > Something I recommend to all serious Unix users is to put the exit status > in the shell prompt. Alternatively, you can indicate a non-zero exit status by displaying a prompt symbol in a different colour than usual. This might be preferable for folks who prefer fixed-width and/or minimalist

Re: .ab oddity

2023-02-04 Thread G. Branden Robinson
Hi Peter, At 2023-02-04T16:09:55-0500, Peter Schaffter wrote: > The reasoning makes sense but now you have to jump through a hoop > when you're using .ab for debugging. I usually debug with the -z > flag. Formerly, > > echo -e ".nr foo 1\n.if r foo .ab\n" | groff -z > > would helpfully spit

Re: .ab oddity

2023-02-04 Thread Peter Schaffter
On Fri, Feb 03, 2023, G. Branden Robinson wrote: > I felt it was unorthogonal for `ab` to force a message onto the > standard error stream when the `tm` request (and groff's several > relatives of it) already existed.[1] > > Part of the idea here is that you can then use `am` to stick an abort >

Re: .ab oddity

2023-02-03 Thread Dave Kemper
http://savannah.gnu.org/bugs/?61070 has more info, including varying behaviors amongst historical (and one modern) troffs.

Re: .ab oddity

2023-02-03 Thread G. Branden Robinson
Hi Peter, At 2023-02-03T15:11:05-0500, Peter Schaffter wrote: > Before I file a bug report, I'm wondering if this is unique to me. > > echo ".ab" | groff -Tutf8 > > does not print "User abort". (".ab foo" correctly prints "foo".) > > My current build is 1.23.0.rc1.3711-25fb. It is not

.ab oddity

2023-02-03 Thread Peter Schaffter
Before I file a bug report, I'm wondering if this is unique to me. echo ".ab" | groff -Tutf8 does not print "User abort". (".ab foo" correctly prints "foo".) My current build is 1.23.0.rc1.3711-25fb. -- Peter Schaffter https://www.schaffter.ca