On 14 Aug 2008, at 10:47, Adam Eberbach wrote:
I have a 300MB file, a text file which is the output of a long SQL run. Years ago I remembered opening such huge files in Visual Studio or Slickedit without much trouble so I tried it - no way, it gave up after grabbing about 1.2GB of RAM and exhausting what was free.
OK, silly thing to do anyway - I got what I needed from the terminal using head and tail. But is this expected behavior? Can't it partially load files and load/dump as you scroll? Eating 4x file size in memory and still not having enough seems a bit excessive.
Not complaining, just curious.
This is my biggest (well, only) complaint about TextMate. I am handling some sql dump files at the moment and TextMate runs out of steam with files bigger than 5 MB. For these bigger files I use Oxygen or Editix. I'd use TextMate for everything if it weren't for this drawback.
Ian. --