A.J.Mechelynck wrote:
Albie Janse van Rensburg wrote:
Hi all
I recently decided to try out the Cream build (sans Cream) of Vim,
with all the new patches (from
http://sourceforge.net/project/showfiles.php?group_id=43866&package_id=39721).
Now, I seem to be unable to edit my vimrc without bringing Vim to a
complete halt! I am unable to break out of it, and the only way to
close Vim is by killing the process (leaving all my buffers' temp
files still lying around, etc. Not very graceful). I suspect the
problem lies with the Vim filetype syntax highlighting, since I do
not get the problem when I have syntax off, or syntax on while
editing other filetypes. When I reverted to the "official" Vim build
for Windows (compiled May 7 2006), the problem disappeared.
Is there anyone on this list that uses the Cream (sans Cream) build
of Vim, and can someone confirm/help solve the problem?
Albie
gvim --version (of the Cream build):
VIM - Vi IMproved 7.0 (2006 May 7, compiled May 3 2007 17:13:26)
MS-Windows 32 bit GUI version with OLE support
Included patches: 1-241
Compiled by [EMAIL PROTECTED]
Big version with GUI. Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset
+cindent
+clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
+comments
+cryptv +cscope +cursorshape +dialog_con_gui +diff +digraphs -dnd
-ebcdic
+emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path
+find_in_path
+folding -footer +gettext/dyn -hangul_input +iconv/dyn +insert_expand
+jumplist
+keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap
+menu
+mksession +modify_fname +mouse +mouseshape +multi_byte_ime/dyn
+multi_lang
+mzscheme/dyn +netbeans_intg +ole -osfiletype +path_extra +perl/dyn
-postscript
+printer -profile +python/dyn +quickfix +reltime +rightleft +ruby/dyn
+scrollbind +signs +smartindent -sniff +statusline -sun_workshop +syntax
+tag_binary +tag_old_static -tag_any_white +tcl/dyn -tgetent
-termresponse
+textobjects +title +toolbar +user_commands +vertsplit +virtualedit
+visual
+visualextra +viminfo +vreplace +wildignore +wildmenu +windows
+writebackup
-xfontset -xim -xterm_save -xpm_w32
system vimrc file: "$VIM\vimrc"
user vimrc file: "$HOME\_vimrc"
2nd user vimrc file: "$VIM\_vimrc"
user exrc file: "$HOME\_exrc"
2nd user exrc file: "$VIM\_exrc"
system gvimrc file: "$VIM\gvimrc"
user gvimrc file: "$HOME\_gvimrc"
2nd user gvimrc file: "$VIM\_gvimrc"
system menu file: "$VIMRUNTIME\menu.vim"
Compilation: gcc -O3 -fomit-frame-pointer -freg-struct-return
-fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG
1. Check (by looking near the top of the files) the versions of the
following files, all of which contribute to vimscript highlighting
(and are sourced whenever a *.vim file is opened with ":filetype
plugin indent on" and "syntax on"):
------ $VIMRUNTIME/ftplugin/vim.vim
" Vim filetype plugin
" Language: Vim
" Maintainer: Bram Moolenaar <[EMAIL PROTECTED]>
" Last Change: 2006 Sep 26
------
------ $VIMRUNTIME/indent/vim.vim
" Vim indent file
" Language: Vim script
" Maintainer: Bram Moolenaar <[EMAIL PROTECTED]>
" Last Change: 2005 Jul 06
------
------ $VIMRUNTIME/syntax/vim.vim
" Vim syntax file
" Language: Vim 7.0 script
" Maintainer: Dr. Charles E. Campbell, Jr.
<[EMAIL PROTECTED]>
" Last Change: April 25, 2007
" Version: 7.0-62
------
------ $VIMRUNTIME/syntax/perl.vim
" Vim syntax file
" Language: Perl
" Maintainer: Nick Hibma <[EMAIL PROTECTED]>
" Last Change: 2006 November 23
" Location: http://www.van-laarhoven.org/vim/syntax/perl.vim
------
------ $VIMRUNTIME/syntax/ruby.vim
" Vim syntax file
" Language: Ruby
" Maintainer: Doug Kearns <[EMAIL PROTECTED]>
" Info: $Id: ruby.vim,v 1.118 2007/03/02 05:40:49 tpope Exp $
" URL: http://vim-ruby.rubyforge.org
" Anon CVS: See above site
" Release Coordinator: Doug Kearns <[EMAIL PROTECTED]>
"
----------------------------------------------------------------------------
"
" Previous Maintainer: Mirko Nasato
" Thanks to perl.vim authors, and to Reimer Behrends. :-) (MN)
"
----------------------------------------------------------------------------
------
------ $VIMRUNTIME/syntax/python.vim
" Vim syntax file
" Language: Python
" Maintainer: Neil Schemenauer <[EMAIL PROTECTED]>
" Updated: 2006-10-15
" Added Python 2.4 features 2006 May 4 (Dmitry Vasiliev)
------
------ $VIMRUNTIME/syntax/tcl.vim
" Vim syntax file
" Language: TCL/TK
" Maintainer: Brett Cannon <[EMAIL PROTECTED]>
" (previously Dean Copsey <[EMAIL PROTECTED]>)
" (previously Matt Neumann <[EMAIL PROTECTED]>)
" (previously Allan Kelly <[EMAIL PROTECTED]>)
" Original: Robin Becker <[EMAIL PROTECTED]>
" Last Change: 2006 Nov 17
"
" Keywords TODO: format clock click anchor
------
------ $VIMRUNTIME/syntax/scheme.vim
" Vim syntax file
" Language: Scheme (R5RS)
" Last Change: Nov 28, 2004
" Maintainer: Sergey Khorev <[EMAIL PROTECTED]>
" Original author: Dirk van Deun <[EMAIL PROTECTED]>
------
All the files in my $VIMRUNTIME match the above.
2. Are there any other files of the same names in the "ftplugin",
"indent" and "syntax" subfolders of any folders mentioned in your
'runtimepath' setting?
I checked through my vimfiles folder in $HOME, nothing came up.
3. Do you have also vim.exe installed, or only gvim.exe? If you have
both, try running vim.exe in a Dos Box to view your _vimrc. Do you get
the same hang?
vim.exe gives the same problem - after asking whether or not to
recover/delete/edit anyway/etc (I chose delete, but it's the same
regardless), it freezes up.
4. If the above checks don't raise a warning signal, try the following
(in a Dos Box):
gvim
:scriptnames
" near the top, do you see your _vimrc?
" What is its path? Write it down.
:q
cd "C:\Program Files\vim\vim70"
gvim -u vimrc_example.vim -U NONE
:e C:/
" you should see the directory listing of C:\
" navigate (by clicking each directory in turn) to the
" directory containing your _vimrc.
" Then click the name of your _vimrc
" Does it open? Is it correctly highlighted?
Vim (Gvim this time) freezes up again.
Best regards,
Tony.
Interestingly enough, it's not like Vim is in an infinite loop, using
more and more memory. Process Explorer reports it to be using 4mb RAM
only, and practically no CPU cycles... odd.
I have also tried just running >G/Vim -u NONE ; and then loading a vimrc
file. As soon as I do :syntax enable, the application freezes up. This
must be a bug in one of the patches since last year, right? As I
mentioned before, the problem does not manifest when I use the "huge"
version from vim.org.
--
Albie Janse van Rensburg ~ http://morph.telspace.co.za
Please don't send me any MS Word or Powerpoint attachments
unless it's absolutely neccessary - send simply text.
http://www.gnu.org/philosophy/no-word-attachments.html
Yes, but which self do you want to be?
