Skip to main content
Topic: a bizarre issue with mandoc (Read 728 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

a bizarre issue with mandoc

I switched from man-db to mandoc a while ago, and just now had my first hiccup, and it sure is strange!
Code: [Select]
$ man gs
"/tmp/man.XXXXx4azr2" may be a binary file.  See it anyway?
If I say yes, I get a screenful of junk. But if I point man directly to the page, it works:
Code: [Select]
$ man -l /usr/share/man/man1/gs.1.gz  #this works!
The warning about a binary file is actually printed by 'less', and the tmp file is just a copy of /usr/share/man/man1/gs.1.gz, so somehow it's not getting decompressed by mandoc.

As far as I can tell, this only happens with 'gs'(!!??); all other man pages work fine, including others in the ghostscript package.

I have run makewhatis. No change.

I guess I'm asking
a) if there is something in my mandoc-noobness that I've failed to understand that's causing this,
and if not
b) whether someone with both mandoc & ghostscript can replicate this, in which case it might be a bug?

 

Re: a bizarre issue with mandoc

Reply #1
Same thing.