Re: Gvim closing unexpectedly

2006-11-08 Thread Edward Wong

Yup, I can confirm it too. I'm in Windows with cygwin and command
:echo has(tcl) crashes gvim.  :)

On 10/5/06, Steve Hall [EMAIL PROTECTED] wrote:

From: Greg Dunn, Thu, October 05, 2006 9:36 am
 On 10/4/06, Steve Hall wrote:
  On Thu, 2006-10-05 at 10:04 +1000, Robbie Gates wrote:
  
   i was having problems with gvim hanging when i tried to edit my
   vimrc. After a bit of sleuthing, i tracked it down to has(tcl)
   hanging (called from syntax/vim.vim).
 
  It appears your post and one on the vim list are related:
 
http://tech.groups.yahoo.com/group/vim/message/74227
http://tech.groups.yahoo.com/group/vimdev/message/45215

 Yep, I have cygwin, and yep, the dummy tcl84.dll fixed the problem.

I, too, can now confirm that the Cygwin tcl84.dll on path prior to any
others causes :echo has(tcl) to hang.

Can anyone here using a Windows binary different from those packaged
by Cream reproduce this?



--
Steve Hall  [ digitect dancingpaper com ]




Re: Gvim closing unexpectedly

2006-11-08 Thread Edward Wong

Yup, I can confirm it too. I'm in Windows with cygwin and command
:echo has(tcl) crashes gvim.  :)

On 10/5/06, Steve Hall [EMAIL PROTECTED] wrote:

From: Greg Dunn, Thu, October 05, 2006 9:36 am
 On 10/4/06, Steve Hall wrote:
  On Thu, 2006-10-05 at 10:04 +1000, Robbie Gates wrote:
  
   i was having problems with gvim hanging when i tried to edit my
   vimrc. After a bit of sleuthing, i tracked it down to has(tcl)
   hanging (called from syntax/vim.vim).
 
  It appears your post and one on the vim list are related:
 
http://tech.groups.yahoo.com/group/vim/message/74227
http://tech.groups.yahoo.com/group/vimdev/message/45215

 Yep, I have cygwin, and yep, the dummy tcl84.dll fixed the problem.

I, too, can now confirm that the Cygwin tcl84.dll on path prior to any
others causes :echo has(tcl) to hang.

Can anyone here using a Windows binary different from those packaged
by Cream reproduce this?



--
Steve Hall  [ digitect dancingpaper com ]




RE: Gvim closing unexpectedly

2006-10-05 Thread Steve Hall
From: Greg Dunn, Thu, October 05, 2006 9:36 am
 On 10/4/06, Steve Hall wrote:
  On Thu, 2006-10-05 at 10:04 +1000, Robbie Gates wrote:
  
   i was having problems with gvim hanging when i tried to edit my
   vimrc. After a bit of sleuthing, i tracked it down to has(tcl)
   hanging (called from syntax/vim.vim).
 
  It appears your post and one on the vim list are related:
 
http://tech.groups.yahoo.com/group/vim/message/74227
http://tech.groups.yahoo.com/group/vimdev/message/45215

 Yep, I have cygwin, and yep, the dummy tcl84.dll fixed the problem.

I, too, can now confirm that the Cygwin tcl84.dll on path prior to any
others causes :echo has(tcl) to hang. 

Can anyone here using a Windows binary different from those packaged
by Cream reproduce this?



-- 
Steve Hall  [ digitect dancingpaper com ]



Re: Gvim closing unexpectedly

2006-10-05 Thread Greg Dunn

On 10/4/06, Steve Hall [EMAIL PROTECTED] wrote:


[cross-posting to connect threads]

On Thu, 2006-10-05 at 10:04 +1000, Robbie Gates wrote:
 Hi All,

 i was having problems with gvim hanging when i tried to edit my
 vimrc.

 After a bit of sleuthing, i tracked it down to has(tcl) hanging
 (called from syntax/vim.vim).

It appears your post and one on the vim list are related:

  http://tech.groups.yahoo.com/group/vim/message/74227
  http://tech.groups.yahoo.com/group/vimdev/message/45215

I'm not on a Windows box tonight to track this down, can anyone help
us figure out if this is in the binary or runtime?

1. Verify syntax/vim.vim is not corrupt

2. Test the binary:

 :echo has(tcl)

Greg, do you have Cygwin installed?

Interesting that this just cropped up twice in two hours, these
packages have been downloaded nearly 300 times over 8 days.


Yep, I have cygwin, and yep, the dummy tcl84.dll fixed the problem.
One difference I have from the dev thread is that my gvim doesn't
hang, it just closes.

-- Greg


RE: Gvim closing unexpectedly

2006-10-05 Thread Steve Hall
From: Greg Dunn, Thu, October 05, 2006 9:36 am
 On 10/4/06, Steve Hall wrote:
  On Thu, 2006-10-05 at 10:04 +1000, Robbie Gates wrote:
  
   i was having problems with gvim hanging when i tried to edit my
   vimrc. After a bit of sleuthing, i tracked it down to has(tcl)
   hanging (called from syntax/vim.vim).
 
  It appears your post and one on the vim list are related:
 
http://tech.groups.yahoo.com/group/vim/message/74227
http://tech.groups.yahoo.com/group/vimdev/message/45215

 Yep, I have cygwin, and yep, the dummy tcl84.dll fixed the problem.

I, too, can now confirm that the Cygwin tcl84.dll on path prior to any
others causes :echo has(tcl) to hang. 

Can anyone here using a Windows binary different from those packaged
by Cream reproduce this?



-- 
Steve Hall  [ digitect dancingpaper com ]



Re: Gvim closing unexpectedly

2006-10-04 Thread Steve Hall

[cross-posting to connect threads]

On Thu, 2006-10-05 at 10:04 +1000, Robbie Gates wrote:
 Hi All,

 i was having problems with gvim hanging when i tried to edit my
 vimrc.

 After a bit of sleuthing, i tracked it down to has(tcl) hanging
 (called from syntax/vim.vim).

It appears your post and one on the vim list are related:

  http://tech.groups.yahoo.com/group/vim/message/74227
  http://tech.groups.yahoo.com/group/vimdev/message/45215

I'm not on a Windows box tonight to track this down, can anyone help
us figure out if this is in the binary or runtime?

1. Verify syntax/vim.vim is not corrupt

2. Test the binary:

 :echo has(tcl)

Greg, do you have Cygwin installed?

Interesting that this just cropped up twice in two hours, these
packages have been downloaded nearly 300 times over 8 days.



-- 
Steve Hall  [ digitect dancingpaper com ]



Gvim closing unexpectedly

2006-10-04 Thread Greg Dunn

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?


:version

VIM - Vi IMproved 7.0 (2006 May 7, compiled Sep 26 2006 11:09:51)
MS-Windows 32 bit GUI version with OLE support
Included patches: 1-110
Compiled by [EMAIL PROTECTED]
Big version with GUI.  Features included (+) or not (-):
+arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent +cl
ientserver +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 +mzs
cheme/dyn +netbeans_intg +ole -osfiletype +path_extra +perl/dyn -postscript
+printer -profile +python/dyn +quickfix +reltime +rightleft +ruby/dyn +scrollbin
d +signs +smartindent -sniff +statusline -sun_workshop +syntax +tag_binary
+tag_old_static -tag_any_white +tcl/dyn -tgetent -termresponse +textobjects +tit
le +toolbar +user_commands +vertsplit +virtualedit +visual +visualextra
+viminfo +vreplace +wildignore +wildmenu +windows +writebackup -xfontset -xim -x
term_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-redu
ce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG -DWINVER=0x0400 -D_WIN32_WINNT=0x0400 -DFEA
T_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=perl58.dll -DFEAT_PYTHON -DDYNAMIC_PY
THON -DDYNAMIC_PYTHON_DLL=python24.dll -DFEAT_RUBY -DDYNAMIC_RUBY -DDYNAMIC_RU
BY_DLL=msvcrt-ruby18.dll -DDYNAMIC_RUBY_VER=18 -DFEAT_MZSCHEME -DDYNAMIC_MZSCH
EME -DDYNAMIC_MZSCH_DLL=libmzsch352.dll -DDYNAMIC_MZGC_DLL=libmzgc352.dll -D
FEAT_TCL -DDYNAMIC_TCL -DDYNAMIC_TCL_DLL=tcl84.dll -DDYNAMIC_GETTEXT -DDYNAMIC
_ICONV -DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DFEAT_CSCOPE -DFEAT_NETBEANS
_INTG -DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_OLE -march=i386 -Iproto -I/cygdrive
/c/PERL/lib/CORE -I/cygdrive/c/PYTHON24/include -I/cygdrive/c/RUBY/lib/ruby/1.8/
i386-mswin32 -I/cygdrive/c/PROGRA~1/MzScheme/include -I/cygdrive/c/Tcl/include -
s -mno-cygwin
Linking: gcc -s -o gvim.exe  -luuid -lole32 /cygdrive/c/Tcl/lib/tclstub84.lib -l
wsock32 -mwindows -lcomctl32 -lversion -loleaut32 -lstdc++


RE: Gvim closing unexpectedly

2006-10-04 Thread Steve Hall
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 ]



Re: Gvim closing unexpectedly

2006-10-04 Thread Steve Hall

[cross-posting to connect threads]

On Thu, 2006-10-05 at 10:04 +1000, Robbie Gates wrote:
 Hi All,

 i was having problems with gvim hanging when i tried to edit my
 vimrc.

 After a bit of sleuthing, i tracked it down to has(tcl) hanging
 (called from syntax/vim.vim).

It appears your post and one on the vim list are related:

  http://tech.groups.yahoo.com/group/vim/message/74227
  http://tech.groups.yahoo.com/group/vimdev/message/45215

I'm not on a Windows box tonight to track this down, can anyone help
us figure out if this is in the binary or runtime?

1. Verify syntax/vim.vim is not corrupt

2. Test the binary:

 :echo has(tcl)

Greg, do you have Cygwin installed?

Interesting that this just cropped up twice in two hours, these
packages have been downloaded nearly 300 times over 8 days.



-- 
Steve Hall  [ digitect dancingpaper com ]