On 07/12/09 10:43, JD wrote:
> On Dec 3, 7:24 pm, Tony Mechelynck<[email protected]>
> wrote:
>> On 03/12/09 21:16, JD wrote:
>>
>>
>>
>>> Here's the output of version:
>>
>>> VIM - Vi IMproved 7.2 (2008 Aug 9, compiled Dec  3 2009 06:48:09)
>>> Included patches: 1-315
>>> Compiled by [email protected]
>>> Big version with GTK 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
>>> +float +folding -footer +fork() +gettext -hangul_input +iconv
>>> +insert_expand
>>> +jumplist +keymap +langmap +libcall +linebreak +lispindent +listcmds
>>> +localmap
>>> +menu +mksession +modify_fname +mouse +mouseshape +mouse_dec -
>>> mouse_gpm
>>> -mouse_jsbterm +mouse_netterm +mouse_sysmouse +mouse_xterm
>>> +multi_byte
>>> +multi_lang -mzscheme +netbeans_intg -osfiletype +path_extra -perl
>>> +postscript
>>> +printer -profile -python +quickfix +reltime +rightleft -ruby
>>> +scrollbind
>>> +signs +smartindent -sniff +startuptime +statusline -sun_workshop
>>> +syntax
>>> +tag_binary +tag_old_static -tag_any_white -tcl +terminfo
>>> +termresponse
>>> +textobjects +title +toolbar +user_commands +vertsplit +virtualedit
>>> +visual
>>> +visualextra +viminfo +vreplace +wildignore +wildmenu +windows
>>> +writebackup
>>> +X11 +xfontset +xim +xsmp_interact +xterm_clipboard -xterm_save
>>>      system vimrc file: "$VIM/vimrc"
>>>        user vimrc file: "$HOME/.vimrc"
>>>         user exrc file: "$HOME/.exrc"
>>>     system gvimrc file: "$VIM/gvimrc"
>>>       user gvimrc file: "$HOME/.gvimrc"
>>>       system menu file: "$VIMRUNTIME/menu.vim"
>>>     fall-back for $VIM: "/usr/local/share/vim"
>>> Compilation: gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -I/usr/
>>> local/include/gtk12 -I/usr/local/include/glib12 -I/usr/local/include -
>>> I/usr/X11R6/include -I/usr/local/include  -g
>>> Linking: gcc   -L/usr/local/lib -o vim   -L/usr/local/lib -L/usr/X11R6/
>>> lib -lgtk-12 -lgdk-12 -Wl,-E -lgmodule-12 -lglib-12 -lintl -lXi -lXext
>>> -lXt -lm -lncurses  -lintl
>>
>> No perl and no ruby. If the ftplugins assume that you got the interfaces
>> if you edit the files, you're stuck. The versions I have don't seem to,
>> though (ftplugin/perl.vim doesn't call the Vim/Perl interface and
>> ftplugin/ruby.vim properly tests<if has("ruby")>  AFAICT. However, there
>> could be something I didn't notice.
>>
>>
>>
>>> dates of those files:
>>
>>> $VIMRUNTIME/filetype.vim        2009 Dec 3 06:48 (UTC/GMT)
>>> $VIMRUNTIME/ftplugin/perl.vim   2009 Dec 3 06:48
>>> $VIMRUNTIME/ftplugin/ruby.vim   2009 Dec 3 06:48
>>> $VIMRUNTIME/syntax/perl.vim     2009 Dec 3 06:48
>>> $VIMRUNTIME/syntax/ruby.vim     2009 Dec 3 06:48
>>> $VIMRUNTIME/indent/perl.vim     2009 Dec 3 06:48
>>> $VIMRUNTIME/indent/ruby.vim     2009 Dec 3 06:48
>>
>> Sorry, you misunderstood me. I didn't want the modification dates as set
>> out in the directory (which are the dates you installed these files) but
>> the dates mentioned in the _text_ of the files, somewhere near the top,
>> which are the "Last change" dates written there by whoever edited them.
>>
>>
>>
>>> The only custom scripts i have installed are: SyntaxAttr, BufExplorer,
>>> securemodelines and taglist none of which (i believe) are ruby/perl
>>> specific.
>>
>>> When i ran with 'vim -u /usr/local/share/vim/vim72/vimrc_example.vim',
>>> it still hung. Also, gdb hasn't given me a useful backtrace.
>>
>>> With syntax, indent and plugin all off, the file(s) open fine.With
>>> just syntax on, the file(s) open fine. With syntax and indent on, the
>>> file(s) open fine. When i enabled plugin, that's when vim started
>>> hanging. I removed all 4 plugins from .vim/plugin (the only place i
>>> have any plugins) and with 'filetype plugin on', it still hung.
>>
>> You also have the filetype-plugins distributed with Vim, namely
>> $VIMRUNTIME/ftplugin/perl.vim and $VIMRUNTIME/ftplugin/ruby.vim. These
>> are enabled/disabled by "filetype plugin on/off".
>>
>> Best regards,
>> Tony.
>> --
>> "The identical is equal to itself, since it is different."
>>                  -- Franco Spisani
>
> Hey Tony,
>
> Yeah, it appears I did misunderstand you, sorry. Also, sorry i took so
> long responding. I was out-of-town and didn't have my SSH keys with
> me. :D Since the issue only seems to be ftplugin related, i'll just
> paste the last modified dates for those:

Well, sorry _I_ took so long responding, it's just my Vim inbox is so 
full that sometimes I lose track of some threads. (Oldest unread 
currently 2009-11-22)

>
> $VIMRUNTIME/ftplugin/ruby.vim   2008/08/09 17:50:07
> $VIMRUNTIME/ftplugin/perl.vim    17 Jul 2008
>
> Also, I had a friend test this bug on FreeBSD 6.4 and a different
> friend test on FreeBSD 7.1 and the files i was having issues with with
> filetype plugin on worked fine for the blokes on the newer FreeBSD's.
>
> I also just tried with versions/last modified dates:
>
> $VIMRUNTIME/ftplugin/ruby.vim   ruby.vim,v 1.40 2008/06/29 04:18:43
> tpope
> $VIMRUNTIME/ftplugin/perl.vim    20 Jan 2009

These are the ones I have, which are the latest ones on the rsync 
server. Did you check the syntax scripts? I suppose they wouldn't be 
obsolete, though, if you have this.

>
> and i still had the issue. The only idea i have to possibly narrow
> this down is that the bug popped up sometime from vim 7.2.239 and
> 7.2.299, I know that's a quite big range, but I originally had Vim
> installed from ports with version 7.2.239 and AFAIK, everything worked
> great, upgraded to 7.2.299 and this issue started cropping up or i
> just started noticing it.
>

Well, unless you have something Perl- or Ruby-related somewhere (at any 
depth) under $VIM/vimfiles/ and/or ~/.vim/ (and/or in your vimrc and/or 
gvimrc) then I don't know what can have gone wrong.

You wouldn't have a "system vimrc" or "system gvimrc", would you? Check 
their locations near the middle of the ":version" output: on some OSes 
the software distributor installs a system vimrc and/or gvimrc, 
unbeknownst to the users.


Best regards,
Tony.
-- 
Life is like a simile.

-- 
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

Raspunde prin e-mail lui