On Dec 3, 1:46 am, Tony Mechelynck <[email protected]> wrote: > On 03/12/09 05:20, JD wrote: > > > Vim is hardlocking for me on every single run on my FreeBSD 5.4 > > system. I've tried 7.2.299, 7.2.309 and 7.2.315 and all are broken. > > > It appears to compile fine, but on run, it fails to respond to any > > keystrokes and eats nearly 100% of my CPU till I send it a > > SIGKILL...Please help. :) > > > Thanks > > Does it always hang, even if you start it as > > vim -N -u NONE > or > gvim -N -u NONE > ? > > Best regards, > Tony. > -- > Re graphics: A picture is worth 10K words -- but only those to describe > the picture. Hardly any sets of 10K words can be adequately described > with pictures.
It appears to work fine launching vim with -N -u NONE, when not launching with '-N -u NONE', i've so far narrowed it down to 2 filetypes. I tried opening a ruby script, a perl script, a python script and a C++ source file and the only ones that failed and caused vim to lock were the ruby script and the perl script. I moved the affected scripts to a different directory (same dir as the C++ source) and the issue still occurred and as far as i can tell, the permissions on all 4 files are the same. -- You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php
