Christian Brabandt wrote:
> I have never seen something like this.
I have tried again and seem to have a way to reproduce the problem.
In Vim, execute the following two lines (they may wrap here, each line starts
with a colon). This creates file big.tmp which is 155 MB with 5 million lines.
:let x = [repeat('a',20), repeat('b',25), repeat('c',30), repeat('d',35),
repeat('e',40)]
:call writefile(repeat(x, 1000000), 'big.tmp')
Close Vim and start it again. Then execute the following. It edits the big file
and copies 20,000 lines to a new window, then does a substitute to insert the
length of each line.
:e big.tmp
:1,20000y
:vnew
:put
:%s/.*/\=strlen(submatch(0)) . "\t" . submatch(0)/
:nohlsearch
Now sort the 20,000 lines. The result reliably shows obvious corruption on my
Vim 7.4.972.
:sort
I was planning to also execute the following to mimic the sort of things I do
before the problem appears, but they are not necessary at the moment. The above
is sufficient.
:undo
:redo
:sort n
To state the obvious, if you see the corruption, Vim is now unstable and while
it may work for a while, it may crash. Close Vim and start a new instance
before doing any work.
John
--
--
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
---
You received this message because you are subscribed to the Google Groups
"vim_dev" 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.
