Manas <[email protected]> wrote: > Hi, I was recently working on a large CSV file in Vim. I needed to do > some changes in the file and I utilized the recording feature for it. > Recording feature is really awesome and worked well for my use case. > > However working on a file whenever applied on multiple lines, it is slow > till the point where we can actually see the edit being done on every line. > > I would like to know why is it so slow? Has it something to do with the > design pattern? > > Also, is there any consideration of making it faster (if possible)?
It's not exactly clear what the problem is based on your limited description, but my guess is that you are operating on a file that is huge relative to available RAM and the system is starting to swap to accommodate the state save for the undo command. If that's it, disabling undo before you run it might be a good idea. Usually when I hit that limit, I switch to editing via Perl filter. The undo.txt help file has a section on "undo-remarks" that provides guidance on disabling undo effectively to avoid the memory hit. Elijah -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/49NJln4kGszfYt%40panix5.panix.com.
