On 10/4/06, Steve Hall <[EMAIL PROTECTED]> wrote:
From: "Greg Dunn", Wed, October 04, 2006 1:51 pm
>
> I recently grabbed an updated gvim binary (7.0 with patches 1-110)
> from the cream sf site and now gvim closes without warning whenever
> I try to open a .vim script. It seems to have something to do with
> syntax highlighting:
>
> $ gvim -u NONE -U NONE
>
> :filetype on
> :e foo.vim
> :redir > vim.txt
> :se verbose=10
> :syntax on
> Vim closes at this point
>
> the redirect was intended to see what was happening before it
> closes, but the file never gets written to before vim closes.
>
> Any ideas?
I'm unable to reproduce this in our 7.0.118 build from same site (and
used 7.0.110 daily prior). Do you see anything more if you prepend
:debug to that last command?
--
Steve Hall [ digitect dancingpaper com ]
Fresh install of 7.0.118 gives the same results.
Instead of redirecting to a file, I set verbose=20 and redirected to
@*, which seemed to catch everything. There's a whole lot of output,
but here's the last few lines:
============================================================
finished sourcing c:\Program Files\Vim\vim7.0-118\vim70\syntax/python.vim
continuing in c:\Program Files\Vim\vim7.0-118\vim70\syntax\vim.vim
line 515: syn region vimPythonRegion matchgroup=vimScriptDelim
start=+py\%[thon]\s*<<\s*\z(.*\)$+ end=+^\z1$+
[EMAIL PROTECTED]
line 516: syn region vimPythonRegion matchgroup=vimScriptDelim
start=+py\%[thon]\s*<<\s*$+ end=+\.$+ [EMAIL PROTECTED]
line 517: endif
line 518:
line 519: " [-- tcl --] {{{3
line 520: if (has("tcl") || g:vimembedscript) &&
filereadable(expand("<sfile>:p:h")."/tcl.vim")
============================================================
the output is no different whether I use :debug or not.
-- Greg
