Am 2015-07-02 03:14, schrieb wolfv:
This is a weird bug.

When the attached test_vim.txt file is opened in Vim, and scrolled
down to line 372, Vim hangs and consumes 24% of CPU.
This only happens with the attached vimrc and test_vim.txt.  All other
files I tried work nice with the attached vimrc.

The test_vim.txt file works nice if it is:

        * opened in less

        * opened in vi

        * opened in Vim with the last 7 lines of the attached vimrc commented

The test_vim.txt file also works nice if a blank line is inserted on
line 372 like this:

                FILE_CONTENT  FILE_CONTENT  FILE_CONTENT

http://www.linux4windows.com/Articles/linux_concepts_for_beginners5.html

The attached test_vim.txt file is 504 lines long.
I have reproduced the bug by copying lines 360 to line 375 into a new
file, but it only hangs for a couple seconds.  And does not hang if
the last 7 lines of the vimrc are commented.

I am running Vim version 7.4.6.40 on Linux Fedora 22 on hardware
Haswell Intel NUC Kit D54250WYK.

Thank you.

1) Try to reproduce according to the description here:
http://vimhelp.appspot.com/vim_faq.txt.html#faq-2.5

2) I suspect, markdown syntax highlighting is causing this problem for you.
(since it goes away, if you disable setting the filetype)
You can check with the :syntime command, which pattern is slow
(see :h :syntime) and also you might want to try to switch to the old
re-engine (:set re=1 see :h two-engines), to see if this makes a difference.
If this is the case, contact the maintainer of the markdown syntax file.
He can likely assist on how to proceed and hopefully fix the syntax file.

Best,
Christian

--
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to