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
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
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
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
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
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
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.
Try, as root, executing
mandb
This should hopefully update your man database.
Though I have to admit, I'm having problems with the whatis feature, and I'm
trying to figure out when it stopped working - when I updated to the latest
slink or kde. Did your man problems happen after a upgrade ?
Geoffrey L. Brimhall wrote:
Try, as root, executing
mandb
This should hopefully update your man database.
Though I have to admit, I'm having problems with the whatis feature, and I'm
trying to figure out when it stopped working - when I updated to the latest
slink or kde. Did your
Dear Fellow Debian Users:
(let me know if I've posted this to the wrong place; I don't think
it's a Debian bug per-se, but a local installation problem I can't
solve).
I'm running Debian-1.3 on two machines, my home computer and my
work computer. My home computer runs man just fine,
Are you using bash as your shell and have 'set -a' in /etc/profile or in any
of your bash startup files? If so, try removing 'set -a' or running man under
some other shell.
Bash hanging with man when 'set -a' was in use was reported as bug #8390
during last summer.
// Heikki
--
Heikki
11 matches
Mail list logo
