Hi Conor,
I checked (just to make sure) man procmail, man procmailrc, man procmailex,
man groff, man nroff, man col ... and they're all installed.
I also did rpm -q man and I've got man-1.5h-22 installed.
I also did a
man procmail | col -b > procmail.txt 2> errors.txt
I still got the same error msg on screen with nothing in procmail.txt
but the only thing that I got in errors.txt was this line
usage: col [-bfpx] [-l nline]
Any ideas? Thanks.
Horace
On Wed, Mar 07, 2001 at 09:52:15PM +0000, Conor Daly wrote:
> On Wed, Mar 07, 2001 at 10:46:26PM +0800 or so it is rumoured hereabouts,
> Horace G. Friend III thought:
> > Hi Rich,
> >
> > Here's the output from man procmail | col -b > procmail.txt
> >
> > sh: -c: line 2: syntax error: unexpected end of line
> > Error executing formatting or display command.
> > System command (cd /usr/share/man ; (echo -e ".pl 11i"; /usr/bin/gunzip -c
>/usr/share/man/man1/procmail.1.gz | /usr/bin/gtbl | /usr/bin/groff -S -Tlatin1 -mando
>| /usr/bin less -isr) exited with status 2.
> > No manual entry for procmail
> Do you get anything from
>
> man procmail
>
> ? I'm inclined to think the man page for procmail is not installed. try
> "man ls" (you can be pretty sure of having that manpage..)
>
> >
> > That's it. So what happened here and what's next? Thanks.
> >
> > Had a difficult time writing the above. How can I catch these error msgs into a
>text file for reading into another editor such as in here?
>
> Do
>
> man procmail | col -b > procmail.txt 2> errors.txt
>
> The redirector operator ">" works on a number of "streams".
>
> 1. STDOUT ("Standard out" which is the "normal" output from a program)
> Useage: 'command 1> stdout.txt'
> or
> 'command > stdout.txt'
>
> 2. STDERR ("Standard error" which usually carries error/debug messages)
> Useage: 'command 2> stderr.txt'
>
> ">" or "1>" sends standard out to whatever you specify.
> "2>" sends standard error to whatever you specify.
>
