Hi Benjamin,
It might actually be related. If 2html is doing something wrong, it
must only be on certain inputs, because I have a test suite I run it
through that uses an exhaustive set of all the options (except for
font, encoding, and no_progressbar), and have never seen a crash:
http://code.google.com/p/vim-2html-test
Maybe you could give a sample of the input that crashes Vim?
You're right in that it doesn't unconditionally crash, sorry for my
alarming initial message. Unfortunately the cause appears to be an
interaction between the updated 2html.vim script and my Vim profile
(probably an automatic command). This means I get to go through the
whole <manual binary search by disabling blocks of code and checking
whether it still crashes> ritual. I'll get back to you in a few days
once I've checked every permutation of interacting code in my Vim
profile :-(
- Peter Odding
PS. I've already tried :set vbs=15 and :redir > ~/crash.log but the log
file gets cut of somewhere mid sentence without an obvious cause for the
crash in the preceding lines...
--
You received this message from the "vim_dev" 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
