As described on stackoverflow ([1]) I hit a difference in behaviour, from the point of view of the program invoking "mate -w", when TextMate is quit using Cmd-W versus Cmd-Q.
This may be a Snow Leopard oddity, but does anyone here know what might cause the caller to continue after Cmd-W but not after Cmd-Q?
Thanks, Glyn PS. Please feel free to answer here or on stackoverflow for added kudos.
[1] http://stackoverflow.com/questions/1755069/git-commit-a-on-mac-hangs-when-te...
On 18 Nov 2009, at 16:28, Glyn Normington wrote:
This may be a Snow Leopard oddity, but does anyone here know what might cause the caller to continue after Cmd-W but not after Cmd-Q?
Indeed that is because ‘mate’ never gets a “close” signal from TextMate, as ⌘Q bypass the code which would call that.
It isn’t something I’d considered before, the approach taken in 2.0 though does not show this problem.
On 24 Nov 2009, at 11:56, Allan Odgaard wrote:
On 18 Nov 2009, at 16:28, Glyn Normington wrote:
This may be a Snow Leopard oddity, but does anyone here know what might cause the caller to continue after Cmd-W but not after Cmd-Q?
Indeed that is because ‘mate’ never gets a “close” signal from TextMate, as ⌘Q bypass the code which would call that.
That makes sense.
Isn't it odd that this didn't happen on Leopard too?
It isn’t something I’d considered before, the approach taken in 2.0 though does not show this problem.
Interesting. Can you say how the new approach avoids the problem?
Roughly when will 2.0 ship?
Glyn PS. Thanks for replying.
On 24 Nov 2009, at 12:02, Glyn Normington wrote:
Roughly when will 2.0 ship?
http://wiki.macromates.com/FAQ/TextMate2
C --- Caius Durling caius@caius.name +44 (0) 7960 268 100 http://caius.name/
On 24 Nov 2009, at 13:02, Glyn Normington wrote:
Indeed that is because ‘mate’ never gets a “close” signal from TextMate, as ⌘Q bypass the code which would call that.
That makes sense.
Isn't it odd that this didn't happen on Leopard too?
Application shutdown is mainly handled by the Cocoa framework. Apple tries to “optimize” this by not going through normal object destruction — sounds like until Snow Leopard, the object responsible for talking with ‘mate’ was still properly destructed during exit, and thus able to tell ‘mate’ to exit.
It isn’t something I’d considered before, the approach taken in 2.0 though does not show this problem.
Interesting. Can you say how the new approach avoids the problem?
In 2.0 communication happens via sockets, if the server goes down, the client will learn. That is not the case with distributed objects (which 1.x uses).
Roughly when will 2.0 ship?
When it is ready ;) Still a lot of work to do…
Great. Thanks for this info. Good luck with v2.
Glyn On 24 Nov 2009, at 12:34, Allan Odgaard wrote:
On 24 Nov 2009, at 13:02, Glyn Normington wrote:
Indeed that is because ‘mate’ never gets a “close” signal from TextMate, as ⌘Q bypass the code which would call that.
That makes sense.
Isn't it odd that this didn't happen on Leopard too?
Application shutdown is mainly handled by the Cocoa framework. Apple tries to “optimize” this by not going through normal object destruction — sounds like until Snow Leopard, the object responsible for talking with ‘mate’ was still properly destructed during exit, and thus able to tell ‘mate’ to exit.
It isn’t something I’d considered before, the approach taken in 2.0 though does not show this problem.
Interesting. Can you say how the new approach avoids the problem?
In 2.0 communication happens via sockets, if the server goes down, the client will learn. That is not the case with distributed objects (which 1.x uses).
Roughly when will 2.0 ship?
When it is ready ;) Still a lot of work to do…
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
-
Allan Odgaard -
Caius Durling -
Glyn Normington