hi again,
I realize this has been discussed a while back, but AFAIR the issue at the time has supposedly been resolved (threading of the filessystemchecking process)
whenever I switch back to TM (say, after reloading a browser window) to make changes in (say, a page template) i experience a noticable and annoying delay of two to (sometimes) five seconds (on a dual 1GHz G4 system with 1.25Gb RAM) together with a noticable spike in CPU utilization.
until yesterday I just attributed that delay to the fact that I've switched from working remotely via SFTP to WebDAV over HTTPS (on Tiger). Meanwhile I'm hooked on the conveniences of being able to work remotely using projects - so much, that I've moved my entire project to my local machine just to eliminate that nagging delay and keep the project mode - only to find out a day later that the delay is still there...
the project contains well under a hundred files, each moderately sized, nothing fancy there. is there anything I can do on my side of the problem? could you on yours, Allan?
the delay shows itself by having the frontmost (project-) window visble, but its bar grey and inactive.
curious in berlin,
best regards,
tom -- Tom Lazar http://tomster.org
On May 7, 2005, at 22:26, Tom Lazar wrote:
I realize this has been discussed a while back, but AFAIR the issue at the time has supposedly been resolved (threading of the filessystemchecking process)
No -- the threading mentioned in release notes is for loading bundles.
the project contains well under a hundred files, each moderately sized, nothing fancy there. is there anything I can do on my side of the problem? could you on yours, Allan?
Long term, it should be fixed -- short-term you can change to a static project, i.e. instead of dragging a folder into the project drawer, drag the files form the folder. Of course you lose the advantages of folder references.
I'm curious, does this happen each time you switch away and back to TM, or only when something has actually changed in the filesystem?
I have been experiencing the same thing in b5 -- about two seconds for TM to actually become active again after switching away. I thought it might be my file size or number of files open or something but I can't find a direct correlation that is consistent. Two seconds on a dual 2.5GHZ G5 is an awful lot of instructions...
I'm curious, does this happen each time you switch away and back to TM, or only when something has actually changed in the filesystem?
Since things change on my filesystems all the time, I can't really say. It seems pretty consistent, though.
Is there some experiment we could perform, something to profile to give you some hints?
S
On May 7, 2005, at 6:31 PM, Allan Odgaard wrote:
On May 7, 2005, at 22:26, Tom Lazar wrote:
I realize this has been discussed a while back, but AFAIR the issue at the time has supposedly been resolved (threading of the filessystemchecking process)
No -- the threading mentioned in release notes is for loading bundles.
the project contains well under a hundred files, each moderately sized, nothing fancy there. is there anything I can do on my side of the problem? could you on yours, Allan?
Long term, it should be fixed -- short-term you can change to a static project, i.e. instead of dragging a folder into the project drawer, drag the files form the folder. Of course you lose the advantages of folder references.
I'm curious, does this happen each time you switch away and back to TM, or only when something has actually changed in the filesystem?
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Stephen F. Steiner IDC ssteiner@integrateddevcorp.com www.integrateddevcorp.com (603)433-1232
On 5/8/05, Allan Odgaard allan@macromates.com wrote:
On May 7, 2005, at 22:26, Tom Lazar wrote:
I realize this has been discussed a while back, but AFAIR the issue at the time has supposedly been resolved (threading of the filessystemchecking process)
No -- the threading mentioned in release notes is for loading bundles.
the project contains well under a hundred files, each moderately sized, nothing fancy there. is there anything I can do on my side of the problem? could you on yours, Allan?
Long term, it should be fixed -- short-term you can change to a static project, i.e. instead of dragging a folder into the project drawer, drag the files form the folder. Of course you lose the advantages of folder references.
I'm curious, does this happen each time you switch away and back to TM, or only when something has actually changed in the filesystem?
I have exactly the same behaviour running Textmate version 1.1b5 (v1.1b5).
I have a project whose files & drawers are located on a networked drive I mount through Samba. In the project it's a total of 1900+ files and everytime I switch back to TextMate its a delay while it seems to be loading all information necessary to display the different filetypes correctly. In that delay it shows up the projectwindow and the tab with open files and the one active file, albeit all greyed out. When the delay is over the proper colorcoding appears and I can start editing away.
Would be glad if this behaviour could be resolved somehow. :).
David
A question, is my impression correct that TM checks the change status of all the files in the project drawers? Wouldn't only need to check the status of files in the tabs? After all wouldn't they be the only ones with a status change that makes a difference. Then TM could check the filecounts of the various folders that have been expanded. Or am I missing something here (I am sure that there are a lot of things) It does seem that there should be a cascade of priorities, things that one might want to have updated before working, things that can update as one begins work.
On May 8, 2005, at 4:35, Samuel DeVore wrote:
A question, is my impression correct that TM checks the change status of all the files in the project drawers?
Yes, well, it checks the date of each top-level folder, and if the date is different than when one left TM, it goes down a level etc. On network mounted filesystems the date doesn't seems to be reliable, and this check is slow. On a normal filesystem it _should_ really be a fast check, but based on feedback, this isn't the case for all users.
Wouldn't only need to check the status of files in the tabs?
Well, it needs to update the project drawer, and it needs the file list for e.g. cmd-T etc. -- but yes, there's room for improvements, and as previously stated, it will be changed to be more lazy and offload some scanning to separate threads -- but it'll have to wait till I anyway will update the project window for other planned changes and improvements.
On May 8, 2005, at 4:43 AM, Allan Odgaard wrote:
On May 8, 2005, at 4:35, Samuel DeVore wrote:
Wouldn't only need to check the status of files in the tabs?
Well, it needs to update the project drawer, and it needs the file list for e.g. cmd-T etc. -- but yes, there's room for improvements, and as previously stated, it will be changed to be more lazy and offload some scanning to separate threads -- but it'll have to wait till I anyway will update the project window for other planned changes and improvements.
I understand perfectly that you don't want to fix something now that you're going to rewrite soon[tm] anyway. but would it be possible, that one could state as a preference (using a defaults write statement) that TM only checks the open tabs? for the way I work (and perhaps others, too) that would be a great productivity enhancer for the mean time.
or perhaps only do the check if the project drawer is visible (I actually tried that to see, if the delay would disappear together with it)
and a final note: given all that 'heavy weight'-checking that's going on every time i switch back to TM it's kind of disappointing to find that it doesn't seem to pick up changes to currently open files, i.e. when I append something to my to-do list via quicksilver and i switch back to TM, that new line doesn't show up, if the to-do list was open already. i need to switch to another tab and back again to manually enforce the update.
i have actually lost quite a few to-do items this way :( (by adding items in TM before it picked up the change and then saving from TM thus overwriting the item that was on the version of the to-do list on the filesystem)
just though, I'd mention it ;)
best regards,
tom
-- Tom Lazar, http://tomster.org
On May 8, 2005, at 15:14, Tom Lazar wrote:
[...] would it be possible, that one could state as a preference (using a defaults write statement) that TM only checks the open tabs? for the way I work (and perhaps others, too) that would be a great productivity enhancer for the mean time.
But then when should it update the project drawer? You can create a static (thus non-updating) project by dragging files (instead of folders) to the project drawer. If you want to add an entire folder structure as a project you can e.g. create a script as the one attached below, which takes a folder as first argument and writes a tmproj file to stdout. I didn't make it handle special filenames though (like containing quotes).
and a final note: given all that 'heavy weight'-checking that's going on every time i switch back to TM it's kind of disappointing to find that it doesn't seem to pick up changes to currently open files, i.e. when I append something to my to-do list via quicksilver and i switch back to TM, that new line doesn't show up, if the to-do list was open already. i need to switch to another tab and back again to manually enforce the update.
I am not able to reproduce this. When I switch back to TextMate it updates the file if it had no local changes, or ask me, if it did have local changes.
On May 8, 2005, at 4:05 PM, Allan Odgaard wrote:
You can create a static (thus non-updating) project by dragging files (instead of folders) to the project drawer.
ah, I was completely unaware of that (although, now I do recall it being mentioned here previously...)
If you want to add an entire folder structure as a project you can e.g. create a script as the one attached below, which takes a folder as first argument and writes a tmproj file to stdout. I didn't make it handle special filenames though (like containing quotes).
thanks, that script was helpful. I have now created a static project of my current zope product and switching/roundtripping between TM, browsers and Terminal.app is instant now. I'll definitely be able to "live with this" until you rewrite the whole project drawer.
thank you very much for your service,
best regards,
tom
p.s. @mark: I live just around the corner of Helmholtzplatz, I often hang out there with my kids ;-) next time I see somebody with a powerbook i'll step up and ask... *g*
Tom Lazar http://tomster.org
I can confirm this behavior, it's quite a noticeable lag.
On 5/8/05, Allan Odgaard allan@macromates.com wrote:
On May 8, 2005, at 15:14, Tom Lazar wrote:
[...] would it be possible, that one could state as a preference (using a defaults write statement) that TM only checks the open tabs? for the way I work (and perhaps others, too) that would be a great productivity enhancer for the mean time.
But then when should it update the project drawer? You can create a static (thus non-updating) project by dragging files (instead of folders) to the project drawer. If you want to add an entire folder structure as a project you can e.g. create a script as the one attached below, which takes a folder as first argument and writes a tmproj file to stdout. I didn't make it handle special filenames though (like containing quotes).
and a final note: given all that 'heavy weight'-checking that's going on every time i switch back to TM it's kind of disappointing to find that it doesn't seem to pick up changes to currently open files, i.e. when I append something to my to-do list via quicksilver and i switch back to TM, that new line doesn't show up, if the to-do list was open already. i need to switch to another tab and back again to manually enforce the update.
I am not able to reproduce this. When I switch back to TextMate it updates the file if it had no local changes, or ask me, if it did have local changes.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
I didn't get the original message, so I'm replying to this one. Apologies for that.
But then when should it update the project drawer? You can create a static (thus non-updating) project by dragging files (instead of folders) to the project drawer. If you want to add an entire folder structure as a project you can e.g. create a script as the one attached below, which takes a folder as first argument and writes a tmproj file to stdout. I didn't make it handle special filenames though (like containing quotes).
I'm seeing the same problem with my projects - updating the project drawers takes a few seconds. This is especially annoying when I switch between TextMate and the Web browser in very short sequences.
First I also thought about a setting or even a manual update. But my suggestion now would be to do the project refreshing in a separate thread in the background. Is that possible?
Patrice
On 21/07/2005, at 17.08, Patrice Neff wrote:
I didn't get the original message, so I'm replying to this one. Apologies for that.
The original was sent long ago -- this is a known problem, and it will be fixed when folder behavior is changed post 1.1.
In the meantime, switch to static projects if the delay is too frustrating.
On 22/07/2005, at 1.18, Patrice Neff wrote:
In the meantime, switch to static projects if the delay is too frustrating.
Thanks for your reply. But how do I switch to static projects? I didn't find anything at the big search engines or in the help.
This was actually in the part you quoted:
[...] You can create a static (thus non-updating) project by dragging files (instead of folders) to the project drawer. If you want to add an entire folder structure as a project you can e.g. create a script as the one attached below, which takes a folder as first argument and writes a tmproj file to stdout. [...]
So it's in the way you create the project, not a switch.
Am 22.07.2005 um 01:23 schrieb Allan Odgaard:
This was actually in the part you quoted:
Oops, sorry for that.
[...] You can create a static (thus non-updating) project by
dragging files (instead of folders) to the project drawer. If you want to add an entire folder structure as a project you can e.g. create a script as the one attached below, which takes a folder as first argument and writes a tmproj file to stdout. [...]
So it's in the way you create the project, not a switch.
I see. Well in that case I'll probably just bear with the delays until the real fix.
Patrice
On 7/21/05, Allan Odgaard allan@macromates.com wrote:
On 21/07/2005, at 17.08, Patrice Neff wrote:
I didn't get the original message, so I'm replying to this one. Apologies for that.
The original was sent long ago -- this is a known problem, and it will be fixed when folder behavior is changed post 1.1.
Is there a target release date for 1.2? I was wondering because on my lowly iBook the lag can be up to 10-15 seconds even on smallish projects (100+ files) which is rather frustrating. Especially since i don't care for any of the other editors anymore ;)
On 18/08/2005, at 22.54, Tizzle wrote:
Is there a target release date for 1.2?
No.
I was wondering because on my lowly iBook the lag can be up to 10-15 seconds
Then use static projects instead of folder references, as I have proposed every time this subject surfaces -- I even posted a script to make such project from a folder.
<sarcasm>
hey, now that you mention it, the projects drawer IS slow!!!
I dragged the C: drive of my SMB shared windows 98 drive (running in virtual pc on my iMac g3 400MHZ) into textMate and it took a full 30 SECONDS to reference all the files & sub folders!!! And now every time I switch back to it from Word it takes FOREVER to get back to editing my Bittany_Spears.JPG.vbs file!!!
Ug. I guess i'll have to to back to using my bootlegged version of Visual Studio...
</sarcasm>
I wonder how many windows viruses are written on a mac? Hmm... makes you think... :D
On Aug 18, 2005, at 5:21 PM, Allan Odgaard wrote:
use static projects instead of folder references, as I have proposed every time this subject surfaces