Yesterday I installed the os x security update 2008-005.
Now the mate command takes a very long time to run.
For instance if I type "mate ." to open the current folder it can take up to five minutes to complete the command. The length of time to open the directory seems to be proportional to the number of files in the directory.
If I use mate to open a single file it still takes 10-20 seconds.
Also, I don't know if this is related or if it will help diagnose this problem but after the update I noticed another difference in the terminal usage. In my .profile I have export CLICOLOR=1 export LSCOLORS=DxGxcxdxCxegedabagacad But after the update "ls -la" won't use color when printing results.
I wish I could give more information but I don't really know where to begin. Has anyone had any similar experiences.
On Aug 3, 2008, at 1:43 PM, Sean Lynch wrote:
Yesterday I installed the os x security update 2008-005.
Now the mate command takes a very long time to run.
Have you tried removing .profile (and .bash_rc and whatever else is there), then opening a new Terminal and trying again?
Has anyone had any similar experiences.
I've installed the update but haven't had any problems.
Trevor
On 2008-08-03, at 21:53, Trevor Harmon wrote:
Yesterday I installed the os x security update 2008-005.
Now the mate command takes a very long time to run.
Have you tried removing .profile (and .bash_rc and whatever else is there), then opening a new Terminal and trying again?
Has anyone had any similar experiences.
I've installed the update but haven't had any problems.
Seems to work here too. No dramatic change after the SU.
Yesterday I installed the os x security update 2008-005.
Now the mate command takes a very long time to run.
Have you tried removing .profile (and .bash_rc and whatever else is there), then opening a new Terminal and trying again?
Has anyone had any similar experiences.
I've installed the update but haven't had any problems.
Seems to work here too. No dramatic change after the SU.
I DO have this problem. Soon after I typed "mate" into a Terminal window I also had a kernel panic, while Textmate still was unresponsive. Don't know if these are related.
Jonas
On 4 Aug 2008, at 11:24, Jonas Zimmermann wrote:
Yesterday I installed the os x security update 2008-005.
Now the mate command takes a very long time to run.
Have you tried removing .profile (and .bash_rc and whatever else is there), then opening a new Terminal and trying again?
Has anyone had any similar experiences.
I've installed the update but haven't had any problems.
Seems to work here too. No dramatic change after the SU.
I DO have this problem. Soon after I typed "mate" into a Terminal window I also had a kernel panic, while Textmate still was unresponsive. Don't know if these are related.
in the interests of science I typed mate . in a newly opened terminal window - TM started, but went unresponsive - I force quit it and got this in the terminal window:
2008-08-04 11:26:45.271 mate[914:10b] Exception raised during posting of notification. Ignored. exception: 'connection went invalid while waiting for a reply' invoked observer method: '*** -[OakLaunchHelper didLaunchTextMate:]' observer: 0x122730 notification name: 'NSWorkspaceDidLaunchApplicationNotification'
I sent the crash report to macromates (smart Crash Reports)
hth
On 4 Aug 2008, at 11:30, Tony Crockford wrote:
On 4 Aug 2008, at 11:24, Jonas Zimmermann wrote:
Yesterday I installed the os x security update 2008-005.
Now the mate command takes a very long time to run.
Have you tried removing .profile (and .bash_rc and whatever else is there), then opening a new Terminal and trying again?
Has anyone had any similar experiences.
I've installed the update but haven't had any problems.
Seems to work here too. No dramatic change after the SU.
I DO have this problem. Soon after I typed "mate" into a Terminal window I also had a kernel panic, while Textmate still was unresponsive. Don't know if these are related.
in the interests of science I typed mate . in a newly opened terminal window - TM started, but went unresponsive - I force quit it and got this in the terminal window:
Update.
I re-created the symbolic link (from the help menu)
mate . works fine (in a sensible directory) but still goes unresponsive if I invoke it at /~ (which is probably a daft idea!)
it did eventually open my home folder, so it is working fine
On 4 Aug 2008, at 11:30, Tony Crockford wrote:
Update.
I re-created the symbolic link (from the help menu)
mate . works fine (in a sensible directory) but still goes unresponsive if I invoke it at /~ (which is probably a daft idea!)
it did eventually open my home folder, so it is working fine
fix (?) confirmed. "mate folder" works again for me.
Jonas
On 2008-08-04, at 12:40, Tony Crockford wrote:
in the interests of science I typed mate . in a newly opened terminal window - TM started, but went unresponsive - I force quit it and got this in the terminal window:
Update.
I re-created the symbolic link (from the help menu)
mate . works fine (in a sensible directory) but still goes unresponsive if I invoke it at /~ (which is probably a daft idea!)
I confirm. The same here. Daft or not daft, this is not The Right Thing to react so on daft ideas of the user ;-)
The question: did it really begin only after the the latest SU or was it there unnoticed in the past?
P.
On 4 Aug 2008, at 12:15, silverdr@inet.com.pl wrote:
On 2008-08-04, at 12:40, Tony Crockford wrote:
in the interests of science I typed mate . in a newly opened terminal window - TM started, but went unresponsive - I force quit it and got this in the terminal window:
Update.
I re-created the symbolic link (from the help menu)
mate . works fine (in a sensible directory) but still goes unresponsive if I invoke it at /~ (which is probably a daft idea!)
I confirm. The same here. Daft or not daft, this is not The Right Thing to react so on daft ideas of the user ;-)
but it did eventually open it (on my Mac Pro) and given that my home folder contains nearly 700 thousand items (227GB), I think it fair that TM goes and sulks for a bit.
;o)
On 2008-08-04, at 13:26, Tony Crockford wrote:
mate . works fine (in a sensible directory) but still goes unresponsive if I invoke it at /~ (which is probably a daft idea!)
I confirm. The same here. Daft or not daft, this is not The Right Thing to react so on daft ideas of the user ;-)
but it did eventually open it (on my Mac Pro) and given that my home folder contains nearly 700 thousand items (227GB), I think it fair that TM goes and sulks for a bit.
Well - provided that it _has to_ scan the whole dir structure upon startup. Has it? You waited on the Mac Pro while on a G4 I couldn't wait long enough. If that is because of scanning the whole directory tree - wouldn't it be better to scan on as-needed basis? Better both for startup time and memory usage?
-
Jonas Zimmermann -
Sean Lynch -
silverdr＠inet.com.pl -
Tony Crockford -
Trevor Harmon