On Fri, Apr 14, 2006 at 03:11:13PM +0200, Bram Moolenaar wrote:
>
> Benji Fisher wrote:
>
> > The problem is neither python nor plugins. This is the default
> > version compiled on FC2, with Normal features, -python. When I start
> > gvim with
> >
> > :!gvim -u ~/.vimrc ~/.gvimrc
> >
> > there is no segfault and I get the same plugins as if I do
> >
> > $ gvim
> >
> > I only get the segfault with
> >
> > :!gvim
>
> Well, there must be something different.
>
> Check: it doesn't matter how you started the Vim in which you do
> ":!gvim"?
Good question. This works:
$ vim -u NONE
:!gvim
But guess what? This works, too:
$ vim -u ~/.vimrc
:!gvim
Curiouser and curiouser!
> Perhaps you can check what differences there are between using "gvim"
> without arguments (which crashes) and "gvim -u ~/.vimrc -U ~/.gvimrc"
> (which doesn't crash). E.g., with ":scriptnames".
I already tried that, and I repeated it with the above tests.
$ gvim
:redir @a
:scriptnames
:redir END
:put a
Then visually select and yank into @+ (to avoid blank lines). Then
$ vim
:!gvim
and repeat the process (but not into @+) and compare. This is the
closest I can come: there is no way to do :scriptnames in the one that
actually crashes. There should not be any difference, should there?
I do not have a $VIMINIT environment variable. Nor do I have a
system [g]vimrc file.
--Benji Fisher
