On Fri, Feb 19, 2016 at 11:35 AM, <[email protected]> wrote: > I have a text file (dc.epd) that is nearly 8GB. When I open it in gvim.exe > version 1353 the display shows "dc.epd" 0 lines, 0 characters and the file is > truncated to zero characters. I have compiled with Mic. Visual Studio 2015 > compiler using standard makefile. I start gvim with the command: > vim_git\src\gvim.exe dc.epd > Afterwards it looks like this: > dc.epd _____________________________________________________________ 0 19. > 2.2016 11:28:28 > The .swp file: > .dc.epd.swp ________________________________________________________ 0 19. > 2.2016 11:28:28 H > > The start of the file which contains chess positions look like this: > 1B1b1k1Q/1p2r1p1/5p2/p2q2p1/3P2P1/8/PP3P1P/4R1K1 b - - bm Kf7; ce 0; acd 79; > 1b1B1k1Q/1r3p2/2p1r1qp/1pPp1R2/pP6/4PR1P/P5P1/6K1 b - - bm Qg8; ce 0; acd 20; > 1B1b1k2/1b1n1ppp/p1p1p3/1p6/P3P3/2N2P1P/1PP1B1PK/8 w - - bm Bd6+; ce 0; acd > 20; > 1B1b1k2/1B3npp/1p6/p1p5/8/1P4P1/P6P/7K b - - bm Ke7; ce 0; acd 30; > 1B1b1k2/1B3npp/1p6/p1p5/8/1P6/P5PP/7K w - - bm g3; ce 0; acd 32; > 1B1b1k2/1B3npp/1pp5/p7/8/1P6/P5PP/7K b - - bm c5; ce 0; acd 26; > 1B1b1k2/1b6/1p6/p1pN1p2/P1P2P2/1P1R4/7r/3K4 w - - bm Re3; ce 0; acd 25; > 1B1b1k2/1b6/1p6/p1pN1p2/P1P2P2/1P2R3/7r/3K4 b - - bm Kf7; ce 0; acd 23; > 1B1b1k2/1p1r1p2/6p1/1P1P3r/2P1R3/1N4P1/6K1/8 b - - bm Be7; ce 0; acd 21; > 1B1b1k2/1p1r1p2/6p1/NP1P3r/2P1R3/6P1/6K1/8 w - - bm Nb3; ce 0; acd 24; > 1B1b1k2/1p2r1p1/5p2/p2q2pQ/3P2P1/8/PP3P1P/4R1K1 w - - bm Qh8+; ce 0; acd 39; > 1B1b1k2/1p3npp/2p1B3/p7/8/1P6/P5PP/7K w - - bm Bc8; ce 0; acd 33; > 1b1B1k2/1p3r2/p5p1/P1PR4/1P3P2/5KP1/8/8 b - - bm Kg7; ce 0; acd 23; > 1b1B1k2/1p3r2/p5p1/P1PR4/1P3P2/6P1/5K2/8 w - - bm Kf3; ce 0; acd 22; > 1b1B1k2/1p6/1P1p4/P2P1K2/3P4/8/5P2/8 w - - bm Bc7; ce 0; acd 20; > > Regards > Andreas
Vim loads the whole editfile in memory: for this, it needs enough memory both available and addressable. In 32-bit Vim, including "Vim without Cream" even when loaded (via WOW64) on a 64-bit Windows OS, this means it is not possible to edit a file longer than 2 GiB, or even several files whose total length exceeds 2 GiB. 4 GiB might be addressable but I doubt that 32-bit Vim would accept it; anything higher (including your 8-GiB file) requires a higher addressing mode (typically 64-bit) in all three of processor, OS and program. See :help limits :help 'maxmem' :help 'maxmemtot' But IMHO truncating the file is a bug. 64-bit Vim ought to edit it normally (if there is enough live + swap memory), and 32-bit Vim ought to give an error and refuse to edit the file. Best regards, Tony. -- -- 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.
