I suspect that vim is trying to access the system clipboard 10,0000
times -- once for every delete command.
With clipboard=unnamed, every single delete replaces the contents of the Windows clipboard (per the definition of clipboard=unnamed), so your test modifies the clipboard ten thousand times. No wonder it is sluggish!
I was wondering if Bram or other vim developers could comment: is this not a design flaw? If clipboard=unnamed, should system clipboard modification be delayed until the very last modification?
BTW, Tony, thanks for the following tip!
With
:%g/test/d _
the deletes will go to the black hole register and be reflected in neither the OS clipboard nor any of Vim's "permanent" registers, regardless of the 'clipboard' setting. It ought to go even faster then.
--
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
No comments:
Post a Comment