Re: Problem printing man pages (Correction)
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're actually printing man pages to paper (I'm not sure from your post if you mean printing to screen or printing to paper), consider using the -t option to man to generate PostScript output. Sorry, the pages display (to the screen) fine but I am unable to print (to the printer) without them looking like ^[[1mNAME^[[0m Neither this nor your answer above is supposed to happen. Could you tell me exactly what you're doing so that I can try to reproduce it? 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 the control chars for a short time but that was a long time ago. If I do man man | a2ps -2 --catman or man man | a2ps or man man | lpr or man man | lp I used man 'man' as an example. It turns out it was a bad example as the above commands print the man manpages correctly! Changing the 'man man' to 'man apt-file' would be a correct example. So the problem only applies to 'some' man pages and IIRC that was also the case in the original post on this problem months ago. I have just printed the 1st page of about 30 other manpages and can't find another 'example', yet. There goes my 'save the trees' effort. Sorry if this caused you unnecessary work. I get the control characters on each line ( This was 'not' the case 5-6 months ago) When you posted the fix a few months back, my printer had recently bit the dust, but I had seen the problem a week or so before that. I got a new printer (HP LaserJet 6P) for Christmas and noticed that the control character problem was still there. I have been looking for your post on how to fix it since then. Using the ' man -t | lpr -o number-up=2 -P Laser_6P' has fixed it. It isn't as nice a printout as from a2ps but it does get the job done. System here is stable/testing manpages 1.48-2 groff 1.18-7 a2ps 4.13b-16 cupsys 1.1.15-4 Last dist-upgrade this AM. I do see that there is a new cupsys groff in unstable but I don't want to jump there just now.. Hope that this is enough info for you. If not, let me know. -- You forgot to do your backup 16 days ago. Tomorrow you'll need that version. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem printing man pages (Correction)
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 the control chars for a short time but that was a long time ago. If I do man man | a2ps -2 --catman or man man | a2ps or man man | lpr or man man | lp I used man 'man' as an example. It turns out it was a bad example as the above commands print the man manpages correctly! Changing the 'man man' to 'man apt-file' would be a correct example. 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 in `find /var/cache/man -name cat\*` and try again. Cheers, -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem printing man pages (Correction)
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 in `find /var/cache/man -name cat\*` and try again. That must have been, at least, part of it. Prior to receiving your mail I had to take the system down due to a fan failing in the box. Got your mail after I rebooted. Ran the above and only found files in /var/cache/man/cat1 and they were all man pages that had printed correctly. Just tried man apt-file and it now prints to paper corectly. I had forgotten all about the cached man pages. My bad there. Thanks again Colin. I hope this excersize helped someone elso besides me. If I remember, it may find its way into some documentation somewhere too: perhaps groff's README.Debian. It should have occurred to me earlier that caching was a possibility. Have a great weekend!! You too, -- Colin Watson [[EMAIL PROTECTED]] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem printing man pages
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
answered a question about this but, try as I might, I can't find the
original post or the answer.
I'll answer it again then. :-)
It appears that you didn't accept the changes to groff's conffiles.
/etc/groff/man.local and /etc/groff/mdoc.local should both contain the
following macros (there should be copies in /etc/groff/*.dpkg-dist as
well, I think):
.if n \{\
. \ Debian: Map \(oq to ' rather than ` in nroff mode for devices other
. \ than utf8.
. if !'\*[.T]'utf8' \
.tr \[oq]'
.
. \ Debian: Disable the use of SGR (ANSI colour) escape sequences by
. \ grotty.
. if '\V[GROFF_SGR]'' \
.output x X tty: sgr 0
.
. \ Debian: Map \- to the Unicode HYPHEN-MINUS character, to make
. \ searching in man pages easier.
. if '\*[.T]'utf8' \
.char \- \N'45'
.\}
Both /etc/groff/man.local /etc/groff/mdoc.local do have the above
macros, but that is all they have.
There are other ways: setting GROFF_NO_SGR=1 in the environment is a
simple one, or causing your pager to accept ANSI SGR escapes (less will
do so if given the -R option, for instance). The above is probably 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're actually printing man pages to paper (I'm not sure
from your post if you mean printing to screen or printing to paper),
consider using the -t option to man to generate PostScript output.
Sorry, the pages display (to the screen) fine but I am unable to print
(to the printer) without them looking like ^[[1mNAME^[[0m
I usually pipe the man page to a2ps -4 to save trees and even with the
above, they have all the ^[[1mNAME^[[0m stuff. So your reminder that
about man -t is the fix I will have to use. Will still save trees but
will have to pipe to lp -o number-up=4.
Thanks Colin. I have saved your fix to the 'log' so I will not have
to ask again.
HAND
Wayne
--
Bad or missing mouse driver. Spank the cat [Y/N]?
___
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem printing man pages
On Thu, Jan 30, 2003 at 09:53:24AM -0500, Wayne Topa wrote:
Colin Watson([EMAIL PROTECTED]) is reported to have said:
.if n \{\
. \ Debian: Map \(oq to ' rather than ` in nroff mode for devices other
. \ than utf8.
. if !'\*[.T]'utf8' \
.tr \[oq]'
.
. \ Debian: Disable the use of SGR (ANSI colour) escape sequences by
. \ grotty.
. if '\V[GROFF_SGR]'' \
.output x X tty: sgr 0
.
. \ Debian: Map \- to the Unicode HYPHEN-MINUS character, to make
. \ searching in man pages easier.
. if '\*[.T]'utf8' \
.char \- \N'45'
.\}
Both /etc/groff/man.local /etc/groff/mdoc.local do have the above
macros, but that is all they have.
Indeed, that's correct.
There are other ways: setting GROFF_NO_SGR=1 in the environment is a
simple one, or causing your pager to accept ANSI SGR escapes (less will
do so if given the -R option, for instance). The above is probably 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're actually printing man pages to paper (I'm not sure
from your post if you mean printing to screen or printing to paper),
consider using the -t option to man to generate PostScript output.
Sorry, the pages display (to the screen) fine but I am unable to print
(to the printer) without them looking like ^[[1mNAME^[[0m
Neither this nor your answer above is supposed to happen. Could you tell
me exactly what you're doing so that I can try to reproduce it?
Thanks,
--
Colin Watson [[EMAIL PROTECTED]]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem printing man pages
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 your post if you mean printing to screen or printing to paper), consider using the -t option to man to generate PostScript output. Sorry, the pages display (to the screen) fine but I am unable to print (to the printer) without them looking like ^[[1mNAME^[[0m Neither this nor your answer above is supposed to happen. Could you tell me exactly what you're doing so that I can try to reproduce it? 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 the control chars for a short time but that was a long time ago. If I do man man | a2ps -2 --catman or man man | a2ps or man man | lpr or man man | lp I get the control characters on each line ( This was 'not' the case 5-6 months ago) When you posted the fix a few months back, my printer had recently bit the dust, but I had seen the problem a week or so before that. I got a new printer (HP LaserJet 6P) for Christmas and noticed that the control character problem was still there. I have been looking for your post on how to fix it since then. Using the ' man -t | lpr -o number-up=2 -P Laser_6P' has fixed it. It isn't as nice a printout as from a2ps but it does get the job done. System here is stable/testing manpages 1.48-2 groff 1.18-7 a2ps 4.13b-16 cupsys 1.1.15-4 Last dist-upgrade this AM. I do see that there is a new cupsys groff in unstable but I don't want to jump there just now.. Hope that this is enough info for you. If not, let me know. Thanks for your interest and help. Wayne -- The fortune program is supported, in part, by user contributions and by a major grant from the National Endowment for the Inanities. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem printing man pages
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 hour of looking tru the archives, and google, I can't find the post that Colin wrote on how to fix this problem. Any help appreciated. Wayne -- In English, every word can be verbed. Would that it were so in our programming languages. ___ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem printing man pages
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
original post or the answer.
I'll answer it again then. :-)
It appears that you didn't accept the changes to groff's conffiles.
/etc/groff/man.local and /etc/groff/mdoc.local should both contain the
following macros (there should be copies in /etc/groff/*.dpkg-dist as
well, I think):
.if n \{\
. \ Debian: Map \(oq to ' rather than ` in nroff mode for devices other
. \ than utf8.
. if !'\*[.T]'utf8' \
.tr \[oq]'
.
. \ Debian: Disable the use of SGR (ANSI colour) escape sequences by
. \ grotty.
. if '\V[GROFF_SGR]'' \
.output x X tty: sgr 0
.
. \ Debian: Map \- to the Unicode HYPHEN-MINUS character, to make
. \ searching in man pages easier.
. if '\*[.T]'utf8' \
.char \- \N'45'
.\}
There are other ways: setting GROFF_NO_SGR=1 in the environment is a
simple one, or causing your pager to accept ANSI SGR escapes (less will
do so if given the -R option, for instance). The above is probably the
best fix until everything that accepts groff output has been fixed,
though.
By the way, if you're actually printing man pages to paper (I'm not sure
from your post if you mean printing to screen or printing to paper),
consider using the -t option to man to generate PostScript output.
Cheers,
--
Colin Watson [[EMAIL PROTECTED]]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Printing man pages
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
Re: Printing man pages
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 the answer. Hui I've found a way to do it on our Apple LaserWriter: man -Tps manpage | pap -p AppleLaser:LaserWriter Uwe
Re: printing man pages
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 -T ps ls.ps You can do this directly using man, for example, __ man -Tdvi foo.1x ./foo.1x.dvi __ man -Tps man | lpr -T device, --troff-device [=device] This option is used to change groff (or possibly troff's) output to be suitable for a device other than the default. It implies -t. Examples (pro vided with Groff-1.09) include dvi, latin1, X75 and X100. manoj -- The clothes have no emperor. -- C. A. Hoare, about Ada. Manoj Srivastava [EMAIL PROTECTED] http://www.datasync.com/%7Esrivasta/ Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
printing man pages
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 PROTECTED]
Re: printing man pages
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 file with man ls | ul -T dumb ls.txt Alex Y. -- _ _( )_ ( (o___ +---+ | _ 7 |Alexander Yukhimets| \()| http://pages.nyu.edu/~aqy6633/ | / \ \ +---+ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: printing man pages
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 manpage |lpr Bob Bob Nielsen Internet: [EMAIL PROTECTED] Tucson, AZ AMPRnet: [EMAIL PROTECTED] DM42nh http://www.primenet.com/~nielsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
