On Mon, Jun 26, 2006 at 10:56:48PM -0600, Trent Michael Gamblin wrote:
> Benji Fisher wrote:
>
> > I think this is important, but I do not understand it completely.
> >When I try
> >
> >$ man cvs | col -b | less
> >
> >or simply
> >
> >$ man cvs | less
> >
> >I get a similar error message, "Error executing formatting or display
> >command ... " after I exit less. I guess that was sent to stderr? (I
> >am pretty sure that man is /usr/bin/man .) So somehow vim is reading
> >stderr into your buffer instead of stdout?
> >
[snip]
> >This will start up vim without your usual vimrc file. Is the problem
> >still there?
> >
> Almost the same thing. It first says "Output is not a terminal" then
> when I type something
> it shows the same ugly buffer from my first post.
>
> >If the problem goes away, maybe you have some weird
> >setting for your 'shellredir' option or something. What does
[snip]
>
> shell=/bin/bash
> shellredir=>%s 2>&1
> /bin/bash
Well, that looks normal. Eric Arnold's problem was along these
lines.
> > Next, you can try (from an empty buffer)
> >
> >:r! man cvs
> >
> >or
> >
> >:r! man cvs | col -b
> >
> >Do you get the same error message, or do you get the man page?
> >
> >
> I get the same error messages and partial unformatted man page.
>
> Part of the error message is:
> Error executing formatting or display command.
> System command (cd /usr/share/man && (echo ".pl 11i"; /usr/bin/gunzip -c
> '/usr/share/man/man1/cvs.1.gz') | /usr/bin/gtbll | /usr/bin/nroff -c
> --legacy ISO-8859-1 -mandoc 2>/dev/null | col -b | view -c 'set ft=man
> nomod nolist' -) exited with status 256.
> No manual entry for cvs
>
> When I run that command from the shell I get the man page formatted
> perfectly. So I wonder what program is exiting with status 256 and what
> that particular error code means.
>
> BTW, I had to make a symbol link from gtbl to gtbll, since I didn't have
> gtlbll.
We are making progress: the ftplugin/man.vim script is not the
culprit, there is something wrong with :r! .
BTW, I am using FC2, so my system should be similar to yours.
I get a similar error message to the one you quote when, from a
shell, I try
$ man cvs | less
but I only see the error after I quit less. Do you *not* see it in this
context? Not that I know what to do with the answer, but I am hoping
that our systems will work the same way and that we can narrow down
where that error message comes from.
I do not have any great ideas at the moment (and in fact I am
pressed for time) but this might be worth trying:
$ vim -u NONE
:r! man cvs
:set shllquote? shellxquote?
HTH --Benji Fisher
