On 2009-12-09, JD wrote:
> On Dec 9, 4:15 pm, Christian Brabandt <[email protected]> wrote:
> > Hi JD!
> >
> > On Mi, 09 Dez 2009, JD wrote:
> >
> > > Here's the dates for the syntax files, but i somewhat doubt they have
> > > much to do with here since with "syntax on", everything still worked,
> > > and it didn't fail till "filetype plugin on"
> >
> > I haven't read the whole thread, but I wonder whether profiling or
> > setting verbosity could help debug this issue.
> >
> > See :h 'verbose' and :h profile for more information.
> >
> > If you have tried that already, please excuse my objection.
> >
> > regards,
> > Christian
> > --
> > :wq
>
> This is what i get with verbose mode (-V8): http://dpaste.com/131416/
> After line 266 (the last line), that's when vim hangs eating all my
> CPU.
So what happens when you execute that command from a shell prompt?
(perl -e "print join(q/,/,@INC)") >/tmp/vnfCwnV/0 2>&1
When I tried it, replacing "/tmp/vnfCwnV/0" by just "/tmp/vnfCwnV",
I just got the expected file in /tmp containing a comma-separated
list of directories.
Regards,
Gary
--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
