It would be really nice if Textpad allowed me to work on files larger than available memory. Specifically, larger than 4GB on a Win32 machine. Ideally, this would also allow me to work on files larger than free memory without thrashing virtual memory but that's a big ask.
More experiences in editing large files... who creates 10GB text files, anyway?
editing large files
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
I thought the limit was depending on available virtual memory
Not all files opened in TexPad are text. Other files that are binary may be opened up to be viewed and selected text to be filtered/extracted (original file preserved and new file is a lot smaller).
TextPad can also be used to view:-
* dump files from crashed programs/server;
* dump from crashed filesystem (after using a recovery tool);
* data files used by games or other software that is in a proprietry format;
* some office and multimedia files which have human readable text at the start or elsewhere in the file.
Does there need to be an alternative open method for large files (eg. >128MB) where it has to maintain a sliding window view of the file until something is changed. Is it possible to save the edit operations or edited blocks of text/data and process them later or to a temporary file in the background. That would not be easy to implement.The 32-bit edition can handle file sizes up to the limits of virtual memory.
http://www.textpad.com/products/textpad ... tions.html
Not all files opened in TexPad are text. Other files that are binary may be opened up to be viewed and selected text to be filtered/extracted (original file preserved and new file is a lot smaller).
TextPad can also be used to view:-
* dump files from crashed programs/server;
* dump from crashed filesystem (after using a recovery tool);
* data files used by games or other software that is in a proprietry format;
* some office and multimedia files which have human readable text at the start or elsewhere in the file.