>
> echo foo | troff >&-
Erh, yeah, that's… probably gonna cause issues...
I get the same error you reported earlier, but why on Earth are you closing
the file descriptor?
On Tue, 29 Sep 2020 at 06:31, wrote:
> I think there may be a race condition caused by the groff pipeline. Just to
> be
>
> Going the reverse direction, groff=>markup language (e.g. HTML),
> it is equally evident that only conversions from a known macroset
> are going to produce semantically clean results
Forget about macro sets, and focus on the Troff pipeline itself. Here's how
I'd do it:
infer | little-languag
G. Branden Robinson wrote in
<20200927063701.vj6bg474km3ofpfh@localhost.localdomain>:
|At 2020-09-16T01:21:14+0200, Steffen Nurpmeso wrote:
|> C64 had no login. And DMR would not have used it.
|> I am all with Tadziu Hoffmann in this thread.
|
|Did Tadziu comment on this thread? I don't see
I think there may be a race condition caused by the groff pipeline. Just to
be sure, please try
echo foo | troff >&-
My earlier command was causing troff to dump core when its stdout was
closed (by grops exiting) before it finished writing.
—b9
On Mon, Sep 28, 2020 at 7:04 AM G. Brande
On Mon, Sep 28, 2020, Steve Izma wrote:
> I think Larry's point here is that it's not that hard to write a
> script to go from a markup language to groff.
I think the crux of the matter is going from a markup language *to a
specific groff macroset*, not merely "to groff."
A couple of years ago, Y
At 2020-09-28T03:44:41+1000, John Gardner wrote:
> The error I get with groff 1.22.4 is different:
>
> $ echo foo | groff -Pbar
> grops: can't open file 'bar'
I can't reproduce this either, with groff 1.22.4 (Debian) or groff git
HEAD.
Regards,
Branden
signature.asc
Description: PGP signature
