usually you compile debug versions and then run valgrind or such. Or you try to find a old version of vim which does not suffer of this issue.
If I run your script I see the contents of ls -l scrolling by without crash. Can you run ls -al | wc -l and report how many files are in that directory? Maybe that makes a difference. Can you also try sourcing the script manually after Vim has loaded? > talek@talek-desktop:~/crash$ vim -u NONE -c 'source crash.vim' Can you decribe shortly what happens? is ls output printed at least once before the crash? Marc Weber -- 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
