On Thu, Aug 14, 2008 at 11:47 AM, Adam Eberbach aeberbach@mac.com 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.
In the meantime I have learnt that I may not open huge files (I do not complain about that - I still have vim), but there was one bigger problem. I often purely accidentally clicked on such a file while editing other files in the folder, and TextMate crashed. Well, maybe it did not really crash (I don't remember exactly), but it was definitely staled. So I had to force closing it, and lost all the other work in other windows. Even if I saved the files, I still lost the "open windows" and had to open and organize everything from scratch again. Which was pretty annoying. It would be nice if that could be fixed somehow, but I don't want to camplain too much as other features have priority.
One reason why I love Firefox is that despite its frequent crashes, it reopens all the windows that have been open before the crash when I start it again. That would be a nice feature in TextMate. Low priority, but welcome.
Mojca
On Thu, Aug 14, 2008 at 9:37 AM, Mojca Miklavec mojca.miklavec.lists@gmail.com wrote:
In the meantime I have learnt that I may not open huge files (I do not complain about that - I still have vim), but there was one bigger problem. I often purely accidentally clicked on such a file while editing other files in the folder, and TextMate crashed. Well, maybe it did not really crash (I don't remember exactly), but it was definitely staled. So I had to force closing it, and lost all the other work in other windows. Even if I saved the files, I still lost the "open windows" and had to open and organize everything from scratch again. Which was pretty annoying. It would be nice if that could be fixed somehow, but I don't want to camplain too much as other features have priority.
Perhaps "Preferences -> Advanced -> Saving -> Other: [X] Save files when focus is lost" ?
j.
On Aug 14, 2008, at 9:42 AM, Jay Soffian wrote:
On Thu, Aug 14, 2008 at 9:37 AM, Mojca Miklavec mojca.miklavec.lists@gmail.com wrote:
In the meantime I have learnt that I may not open huge files (I do not complain about that - I still have vim), but there was one bigger problem. I often purely accidentally clicked on such a file while editing other files in the folder, and TextMate crashed. Well, maybe it did not really crash (I don't remember exactly), but it was definitely staled. So I had to force closing it, and lost all the other work in other windows. Even if I saved the files, I still lost the "open windows" and had to open and organize everything from scratch again. Which was pretty annoying. It would be nice if that could be fixed somehow, but I don't want to camplain too much as other features have priority.
Perhaps "Preferences -> Advanced -> Saving -> Other: [X] Save files when focus is lost" ?
IIRC, that's not nearly the same thing. It's also potentially dangerous if saving when you don't explicitly save causes issues.
--- David Zhou david@nodnod.net
On 14 Aug 2008, at 15:37, Mojca Miklavec wrote:
On Thu, Aug 14, 2008 at 11:47 AM, Adam Eberbach aeberbach@mac.com wrote:
[...] Can't it partially load files and load/dump as you scroll?
TextMate relies on having the file parsed up-to at least last visible character. This is needed not just for display, but resolving key strokes, certain preferences items etc.
Additionally it relies on having cached info that allows it to reparse only what is necessary, when the user edits the document at any arbitrary place.
Disk-mapped files can most likely only be supported by introducing a parallel feature-limited mode. This approach has many disadvantages, so it’s rather low on the list.
[...] Even if I saved the files, I still lost the "open windows" and had to open and organize everything from scratch again. Which was pretty annoying. It would be nice if that could be fixed somehow [...]
Complete session restore, including state of modified files, is OTOH pretty high on the list.
On Fri, Aug 15, 2008 at 12:03 AM, Allan Odgaard mailinglist@textmate.org wrote:
Complete session restore, including state of modified files, is OTOH pretty high on the list.
Does that include full undo history restored across editing sessions? Will there be any way to sync that state across machines? No real user-level feature necessarily, just some cache files that can be sync'd or something.
Thanks
On 17 Aug 2008, at 23:41, Thomas Aylott wrote:
On Fri, Aug 15, 2008 at 12:03 AM, Allan Odgaard wrote:
Complete session restore, including state of modified files, is OTOH pretty high on the list.
Does that include full undo history restored across editing sessions? Will there be any way to sync that state across machines? No real user-level feature necessarily, just some cache files that can be sync'd or something.
In this case, a dialog asking for confirmation when you are going to open a very huge file would be very usefull.
El 15/08/2008, a las 6:03, Allan Odgaard escribió:
On 14 Aug 2008, at 15:37, Mojca Miklavec wrote:
On Thu, Aug 14, 2008 at 11:47 AM, Adam Eberbach aeberbach@mac.com wrote:
[...] Can't it partially load files and load/dump as you scroll?
TextMate relies on having the file parsed up-to at least last visible character. This is needed not just for display, but resolving key strokes, certain preferences items etc.
Additionally it relies on having cached info that allows it to reparse only what is necessary, when the user edits the document at any arbitrary place.
Disk-mapped files can most likely only be supported by introducing a parallel feature-limited mode. This approach has many disadvantages, so it’s rather low on the list.
Am 21.08.2008 um 10:25 schrieb argaijo:
In this case, a dialog asking for confirmation when you are going to open a very huge file would be very usefull.
Which TM version do you are using? The latest one asks for confirmation.
--Hans
BTW With my Mac I have no problem with files up to 60 MB even with syntax highlighting.
UPS, my fault, I am updated, but I had not tried to open huge files since some versions ago, perhaps because I already knew that it is not a good idea ; )
El 21/08/2008, a las 10:53, Hans-Jörg Bibiko escribió:
Am 21.08.2008 um 10:25 schrieb argaijo:
In this case, a dialog asking for confirmation when you are going to open a very huge file would be very usefull.
Which TM version do you are using? The latest one asks for confirmation.