Follow-up Comment #9, bug #67612 (group groff):

[comment #8 comment #8:]
> [comment #7 comment #7:]
>> Is use of exit status 4 necessary?  Is _gropdf_ already using
>> status 3 for something?
> 
> The exit status is coming from groff, not gropdf; I presume groff is munging
> it in some manner as the documentation you quoted implies, although the
> specific munging does not seem to be exactly in line with that snippet,
> unless one reads "setting bit 2 if a command exited with a failure status" as
> also implying "and clearing whatever bits the failing command returned on
> exit."

Oh, I misunderstood which command's exit status you were speaking of.
 
> Lacking a test-gropdf analogue to the test-groff script, running the latest
> gropdf directly is not straightforward.

> $ echo 'Yo!' | $HOME/groff/build/test-groff -Z -Tpdf |
> $HOME/groff/build/gropdf
> gropdf: fatal error: failed to open 'download' file


> There's probably a way to make it work, but it's not worth my time to figure
> out, since all I care about is "is it 0 or not-0?"

Hmm.  This works for me:


$ echo 'Yo!' | ./build/test-groff -Z -Tpdf | ./build/gropdf >/dev/null
$ echo $?
0


Let me see if it still works when my current working directory is in some
arbitrary place.


$ echo 'Yo!' | ~/src/GIT/groff/build/test-groff -Z -Tpdf |
~/src/GIT/groff//build/gropdf >/dev/null
$ echo $?
0


This is _groff_ HEAD, as pushed today.  No new commits in my working copy yet.
 But I also can't think of any recent commits that would have changed this.
(_pdfmom_ is not involved.)

Is your _devpdf/dowload_ situation damaged?


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?67612>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to