Andrei Voropaev wrote:
> I've hit one interesting problem. When I've tried to send in an email
> large hexdump (around 50K) the vim entered endless loop with 100% CPU
> usage. I could terminate this loop by hitting Ctrl-C, but as soon as
> I've tried to move to the long line the same thing happened again.
>
> Since I could manipulated this file with vim without mail ftplugin, I
> came to conclusion that the problem has something to do with that
> plugin. The file in question is located at
> http://vandal.sdf-eu.org/hexdump.txt
>
> To reproduce the problem I did the following steps
>
> bash$ vim mutt-vandal-1001-25710-908
>
> :new hexdump.txt
> 2yy
> :q
> p
>
> At this point vim freezes and top reports that it uses 100% CPU.
>
> Just in case. I use ~/.vim/ftplugin/mail.vim with
> set fo-=l
>
> Can anyone else try and see if the same thing happens?
It's the syntax highlighting. Do ":syn clear" and the problem goes
away.
There must be some item in the mail syntax highlighting that can't
handle long lines. Perhaps you can have a look at
$VIMRUNTIME/syntax/mail.vim. Delete some lines to check which one
causes trouble.
The planned improvements to the regexp code (part of the Google summer
of code) should also help. But it will takes several months before we
get something.
--
hundred-and-one symptoms of being an internet addict:
49. You never have to deal with busy signals when calling your ISP...because
you never log off.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
