On Wed, Oct 07, 2009 at 07:31:51AM -0700, rdp wrote: > > I thought the FAQ entry was for OS 10.1 ;-). Unbelievable that such OS > limits are still in place in 2009. > > Back to vi! Seems like the BSD command line tools are not restricted > by this limits and according to activity monitor it loads the whole > file into RAM.
No, I don't believe vim (a.k.a. vi) loads the entire file into RAM. It copies the file into a temporary file with a .swp file extension and then uses mmap() to associate sections of that file with process memory addresses. If for some reason vim gets killed before the user writes updates to disk one can use "vim -r" to find the swapfile and resume where one left off. BTDT many times. BBedit is a great tool. Vim is a great tool. I'd hate to be without both. This email was composed in vim and sent with mutt over an ssh link opened from Terminal.app. -- David Kelly N4HHE, [email protected] ======================================================================== Whom computers would destroy, they must first drive mad. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. -~----------~----~----~----~------~----~------~--~---
