> I've fixed the issue with the title coming out as LS("1") by removing the
> quotes, so it is LS(1) now, but I don't think that's what you want.
Right. That is not what I want. But could you create a version that
doesn't generate the title?
--
Regards,
Peng
On Tue 16 Jun 2015 15:15:27 Peng Yu wrote:
> Yes. It can generate the pdf. But the title is "LS("1")". How to
> remove the title?
It may be that if the title is removed some pdf viewers may show the title as
"Untitled". All the viewers I have tried use the filename if a specific title
is not giv
> Does the pdf /tmp/ls.pdf look alright in the viewer.
Yes.
> The warnings you are seeing are to do with the pdf overview pane where you
You mean "bookmarks"?
> can click on different sections to jump to that section, it should not
> affect the rest of the pdf. You can suppress all warnings wit
On Tue 16 Jun 2015 11:47:27 Peng Yu wrote:
> I am on Mac. I have installed groff using homebrew.
>
> $ ls -lgo $(type -P groff)
> lrwxr-xr-x 1 32 Jun 16 11:08 /usr/local/bin/groff ->
> ../Cellar/groff/1.22.3/bin/groff
>
> Now, I see the following error. What do they mean and how to fix them?
> Th
On Tue, Jun 16, 2015 at 9:51 AM, Dale Snell wrote:
> On Mon, 15 Jun 2015 10:20:16 -0500, in message
> CABrM6wk=CwdfeHVE0YfvdEUSrJ5tA67Y4iUWQ=lcbvfsm_3...@mail.gmail.com,
> Peng Yu wrote:
>
>> > pdfman < $(man -w ls) | groff -Tpdf -mandoc -c > /tmp/ls.pdf
>>
>> I got this error. Do you know what is
Hi Dale,
> If you're running a Debian-based system, synaptic or apt can give you
> the same information. I don't know how to use them, though, so I
> can't provide any examples.
dpkg -l 'groff*'
Cheers, Ralph.
On Mon, 15 Jun 2015 10:20:16 -0500, in message
CABrM6wk=CwdfeHVE0YfvdEUSrJ5tA67Y4iUWQ=lcbvfsm_3...@mail.gmail.com,
Peng Yu wrote:
> > pdfman < $(man -w ls) | groff -Tpdf -mandoc -c > /tmp/ls.pdf
>
> I got this error. Do you know what is wrong?
>
> groff: can't find `DESC' file
> groff:fatal erro
On Tue 16 Jun 2015 11:49:23 Steffen Nurpmeso wrote:
> Anyway i finally have to say that it is a pity that, instead of
> (making the engine as such multi-pass and) instrumenting the
> macros for different output formats that need meta-information,
> and extending the macros sets to include more meta
Anyway i finally have to say that it is a pity that, instead of
(making the engine as such multi-pass and) instrumenting the
macros for different output formats that need meta-information,
and extending the macros sets to include more meta-information
that may be usable in output devices, so many o
