File size is ~6.5MB. It's a binary file with no line breaks, so Vim sees it as one huge line.
I tried to use gqq to allow myself to view the content, and got unrecoverable errors (either lockup, unresponsive to keyboard input, even though GUI menus work, or continual cycle of errors; either way I needed to kill Vim with the task manager). My normal gvim configuration gave: E342: Out of memory! (allocating 6496256 bytes) E323: line count wrong in block 1 E293: block was not locked Press ENTER or type command to continue ??? Press ENTER or type command to continue E293: block was not locked Press ENTER or type command to continue ??? ??? ??? E293... Here, a cycle of ??? and E293 messages popped up and never stopped popping up. The ??? got error highlighting. gvim -N -u NONE -i NONE gave, after: :set nowrite :set tw=80 :set nowrap gqq E342: Out of memory! (allocating 6463488 bytes) E323: line count wrong in block 1 Press ENTER or type command to continue E316: ml_get: cannot find line 637 Finally, after looking at :help E342, I tried in addition to the above options on gvim -N -u NONE -i NONE, these: :set undolevels=-1 :set undoreload=0 I get: E342: Out of memory! (allocating 6463488 bytes) E323: line count wrong in block 1 Press ENTER or type command to continue E323: line count wrong in block 1 Press ENTER or type command to continue ... This time, with CTRL-C, I can eventually get to the point where :q! succeeds in killing Vim. "Vim without Cream" gvim.exe, on 64-bit Windows XP: VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Oct 13 2011 13:41:38) MS-Windows 32-bit GUI version with OLE support Included patches: 1-338 Compiled by [email protected] Huge version with GUI. Features included (+) or not (-): -- 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
