On Fri, Jan 31, 2003 at 04:31:53PM -0500, Wayne Topa wrote:
> Colin Watson([EMAIL PROTECTED]) is reported to have said:
> > I bet I know what's happened, then: you have some old cat pages in
> > /var/cache/man that were cached with a groff that output the ANSI SGR
> > escapes. Clean out everything
Colin Watson([EMAIL PROTECTED]) is reported to have said:
> On Fri, Jan 31, 2003 at 09:47:32AM -0500, Wayne Topa wrote:
> > Wayne Topa([EMAIL PROTECTED]) is reported to have said:
<-- Snip -->> >
> > I used man 'man' as an example. It turns out it was a bad example as
> > the above commands pri
On Fri, Jan 31, 2003 at 09:47:32AM -0500, Wayne Topa wrote:
> Wayne Topa([EMAIL PROTECTED]) is reported to have said:
> > Not sure I get what you mean but here is what is happening.
> > I can do 'man man' and it displays fine on the screen ie no formating
> > characters. I do recall it did display
Wayne Topa([EMAIL PROTECTED]) is reported to have said:
> Colin Watson([EMAIL PROTECTED]) is reported to have said:
> > On Thu, Jan 30, 2003 at 09:53:24AM -0500, Wayne Topa wrote:
> <
> --snip fix from previous post -->
> > >
> > > > By the way, if you&#x
Colin Watson([EMAIL PROTECTED]) is reported to have said:
> On Thu, Jan 30, 2003 at 09:53:24AM -0500, Wayne Topa wrote:
<
--snip fix from previous post -->
> >
> > > By the way, if you're actually printing man pages to paper (I'm not sure
> > > from
ably the
> > best fix until everything that accepts groff output has been fixed,
> > though.
>
> Thats the 'fix' I (now) remember reading. I have added that to
> .bash_profile, sourced bash_profile, and the control chars persist
>
> > By the way, if you
Colin Watson([EMAIL PROTECTED]) is reported to have said:
> On Wed, Jan 29, 2003 at 05:26:16PM -0500, Wayne Topa wrote:
> > I'm having a problem printing man pages. They print with a leading 1m
> > and other *m's and are really tough to read. I remember Colin
> >
On Wed, Jan 29, 2003 at 05:26:16PM -0500, Wayne Topa wrote:
> I'm having a problem printing man pages. They print with a leading 1m
> and other *m's and are really tough to read. I remember Colin
> answered a question about this but, try as I might, I can't find the
>
I'm having a problem printing man pages. They print with a leading 1m
and other *m's and are really tough to read. I remember Colin
answered a question about this but, try as I might, I can't find the
original post or the answer.
Sorry to bother the list with this but after an
> >could someone please tell me how to print man pages? I have access to an
> >Apple LaserWriter over netatalk or to a Epson Stylus Color 1520 over
> >tcp/ip.
> ...
>
> Don't recall the exact command, Uwe, but I do know that if you type `man
> man' then you'll get an ear-full which will include t
Hi there,
could someone please tell me how to print man pages? I have access to an
Apple LaserWriter over netatalk or to a Epson Stylus Color 1520 over
tcp/ip.
Thanks in advance,
Uwe
Hi,
>>"Alex" == <[EMAIL PROTECTED]> writes:
>> Can anyone explain me how can i print a man page? Is there any utility
>> program for this?
Alex> You may convert the source of the man page to postscript file
Alex> and then print it, like:
Alex> zcat /usr/man/man1/ls.1.gz | groff -tmandoc
On Tue, 23 Jun 1998, Tiago Severina wrote:
> Can anyone explain me how can i print a man page? Is there any utility
> program for this?
man -t |lpr
Bob
Bob Nielsen Internet: [EMAIL PROTECTED]
Tucson, AZ AMPRnet: [EMAIL PROTECTED]
DM42nh
> Can anyone explain me how can i print a man page? Is there any utility
> program for this?
Sure.
You may convert the source of the man page to postscript file and then print
it, like:
zcat /usr/man/man1/ls.1.gz | groff -tmandoc -T ps > ls.ps
You may also convert man page to a plain test f
Can anyone explain me how can i print a man page? Is there any utility
program for this?
Tiago Severina.
[EMAIL PROTECTED] http://khonan.sc.uevora.pt/~ts/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTE
15 matches
Mail list logo
