I've been spoiled using all my TextMate macros and snippets in Mail in recent years. Unfortunately, after upgrading to Mountain Lion, Edit in TextMate is no longer working in TM 1.5.11 (1634) with Mail.app v6.0.
IIRC for past Mac OS upgrades, I've fixed this by re-installing Edit in TextMate via the TextMate bundle, making sure /Library/InputManagers is owned by root, then setting Mail.app to launch in 32-bit mode to enable InputManagers. But now in Mountain Lion I don't see the option under Mail > Get Info to launch Mail in 32-bit mode anymore.
1) Does anyone have a workaround for TM1?
2) Does TM2 (which I've not installed yet) have an upgrade/replacement for Edit in TextMate?
Thanks--jon ______________________________ It's not too late to catch up to the 21st century Digital Curation online certificate http://DigitalCuration.UMaine.edu
On 04/08/2012, at 12:39 AM, Jon Ippolito jippolito@maine.edu wrote:
I've been spoiled using all my TextMate macros and snippets in Mail in recent years. Unfortunately, after upgrading to Mountain Lion, Edit in TextMate is no longer working in TM 1.5.11 (1634) with Mail.app v6.0.
IIRC for past Mac OS upgrades, I've fixed this by re-installing Edit in TextMate via the TextMate bundle, making sure /Library/InputManagers is owned by root, then setting Mail.app to launch in 32-bit mode to enable InputManagers. But now in Mountain Lion I don't see the option under Mail > Get Info to launch Mail in 32-bit mode anymore.
As far as I am aware, this is no longer possible as Mountain Lion has dropped support for the 32-bit kernel (http://arstechnica.com/apple/2012/07/os-x-10-8/2/#purchase-and-installation). I assume this also means that 32-bit mode is gone now (though I don't know this for a fact). Maybe Allan can confirm?
Adam
On Aug 6, 2012, at 5:15 AM, Adam Sharp adsharp@me.com wrote:
[…] I assume this also means that 32-bit mode is gone now (though I don't know this for a fact). Maybe Allan can confirm?
32 bit apps can still run, but Apple no longer provide a 32 bit version.
So Edit in TextMate needs to be recompiled as 64 bit (or universal). But I have not tested if input managers work at all in Mountain Lion.
The source for the input manager is here: https://github.com/textmate/edit-in-textmate
It might require some code changes for it to build as 64 bit (with the 10.7/10.8 SDK). I haven’t looked into this yet myself and it’ll probably be a little while before I have a moment to do so, so anyone with the capabilities please jump in! :)
Alternatively there is the QuickCursor commercial application ($5) that might offer similar functionality (I have not tried it myself).
Kind regards Allan
Alan wrote...
Alternatively there is the QuickCursor commercial application ($5) that
might offer similar functionality (I have not tried it myself).
Quick Cursor works really well with TM2, in my experience: you just need to add the bundle id for TM2, which is
com.macromates.textmate.preview
into the preferences (and set an appropriate keyboard shortcut to edit in TM2).
Cheers, Paul
On Sat, Aug 11, 2012 at 11:31 PM, Paul McCann pmccann@gmail.com wrote:
Alan wrote...
s/Alan/Allan/
Sorry, it's late here...
Cheers, Paul
On Aug 11, 2012, at 9:53 AM, Allan Odgaard wrote:
Alternatively there is the QuickCursor commercial application ($5) that might offer similar functionality (I have not tried it myself).
Just as an FYI...
QuickCursor is built around the "ODB Editor Suite", which is built using Apple Script. I added support for it in my text editor (MultiMarkdown Composer), but soon discovered that it does not appear to be compatible with sandboxing. Depending on what happens with Mountain Lion, the App Store, and sandboxing rules, new versions of applications may or may not be able to make use of it. (Not to mention that I've had a ton of trouble getting ODB to play nice with Lion for other reasons, though it appears some developers have it working properly).
QuickCursor is a fantastic app (I would expect nothing less from Jesse), but the ODB protocol is outdated. Brett Terpstra's nvAlt uses a different approach to handle a similar process that should be compatible with sandboxing rules in the future, and IMHO is a better approach. When there is enough interest, I suspect there will be a successor to the ODB protocol that should be easier to implement and avoids all of the sandboxing issues.
F
On Aug 11, 2012, at 4:45 PM, Fletcher Penney wrote:
[…] QuickCursor is a fantastic app (I would expect nothing less from Jesse), but the ODB protocol is outdated. Brett Terpstra's nvAlt uses a different approach to handle a similar process that should be compatible with sandboxing rules in the future, and IMHO is a better approach.
nvAlt seems to be his fork of Notational Velocity.
You mean he uses a different protocol to call upon external editors, or allow others to use nvAlt as editor?
When there is enough interest, I suspect there will be a successor to the ODB protocol that should be easier to implement and avoids all of the sandboxing issues.
For the records, while TM2 supports ODB it also offers a socket interface which is what ‘mate’ and even ‘rmate’ (over ssh) use. I believe this should be compatible with App Store rules.
In theory, other editors could implement the same protocol and users would be able to use ‘rmate’ with their editor of choice.
Though it would probably be better to work together to define a protocol that everyone is happy with, but sockets is likely the way to go about it. This also means that one can install a launchd job to launch the application on demand — this can actually be made to work ATM so running ‘rmate’ over ssh will launch TextMate (if not already running).
On Aug 11, 2012, at 11:34 AM, Allan Odgaard wrote:
On Aug 11, 2012, at 4:45 PM, Fletcher Penney wrote:
[…] QuickCursor is a fantastic app (I would expect nothing less from Jesse), but the ODB protocol is outdated. Brett Terpstra's nvAlt uses a different approach to handle a similar process that should be compatible with sandboxing rules in the future, and IMHO is a better approach.
nvAlt seems to be his fork of Notational Velocity.
Correct - I forget not everyone uses nvAlt instead of NV... ;)
You mean he uses a different protocol to call upon external editors, or allow others to use nvAlt as editor?
Brett could explain it better, but my understanding from our conversations and my own testing is that when nvAlt calls on an external editor, it basically tells the other application to open the file in question. nvAlt monitors that file, and if changes are saved, it updates the copy in it's database. This means that the external editor does not even need to know it is being "used" in this way. I discovered this when I found I could use my editor externally for nvAlt without any special coding - it just worked.
There are some potential issues that would need to be better defined:
* How long does an app continue to monitor a file before assuming it has been abandoned? * What happens if the file is edited and saved, but left open? ODB (IIRC) requires the document to be closed in order to send a signal to the original app that the file has been modified. In this approach, that is no longer necessary.
When there is enough interest, I suspect there will be a successor to the ODB protocol that should be easier to implement and avoids all of the sandboxing issues.
For the records, while TM2 supports ODB it also offers a socket interface which is what ‘mate’ and even ‘rmate’ (over ssh) use. I believe this should be compatible with App Store rules.
In theory, other editors could implement the same protocol and users would be able to use ‘rmate’ with their editor of choice.
Though it would probably be better to work together to define a protocol that everyone is happy with, but sockets is likely the way to go about it. This also means that one can install a launchd job to launch the application on demand — this can actually be made to work ATM so running ‘rmate’ over ssh will launch TextMate (if not already running).
I think a new standard is much needed. I am not particularly invested in what that standard is, but think it should:
* Be easy for 3rd party developers to integrate - adding ODB support required more effort on my part than it should have, and the sample code was not really helpful
* Avoid Applescript
* Avoid requiring code in the external editor, if possible (Brett's approach in nvAlt, while not perfect, doesn't place any burden on the external editor - it simply opens and saves a file without having to be aware that another app is "pulling the strings")
* Be full compatibly with sandboxing rules, just in case
F-
On Aug 11, 2012, at 5:56 PM, Fletcher Penney wrote:
You mean he uses a different protocol to call upon external editors, or allow others to use nvAlt as editor?
[…] nvAlt monitors that file, and if changes are saved, it updates the copy in it's database
Ah OK. This is pretty limited though, e.g. do ‘mate -h’ and you’ll see that there is a need for two-way communication.
[…]
- Be easy for 3rd party developers to integrate - adding ODB support required more effort on my part than it should have, and the sample code was not really helpful
I think the main issue with ODB is that it rely on an AppleEvent that Cocoa events actually doesn’t get to see, because it is abstracted away into application delegate methods (but they need some info that the delegate methods don’t get).
I use this a lot, and recommend it to anyone who asks.
Walter
On Aug 11, 2012, at 9:53 AM, Allan Odgaard mailinglist@textmate.org wrote:
Alternatively there is the QuickCursor commercial application ($5) that might offer similar functionality (I have not tried it myself).