This is nothing to do with the recent update.
I use Gnu screen a fair bit to avoid having terminals open all over my screen. I have found that from within a screen session, if I type ``mate some_file.txt'' TextMate gets launched (if not already running) or brought to focus with a new window, but the file is not opened and the command failes with ``mate: failed to establish a connection with TextMate.''
The initial call to TM is working because TM activated. Any ideas how to make the next step work?
On 16 Nov 2010, at 17:49, Justin Catterall wrote:
[...] The initial call to TM is working because TM activated. Any ideas how to make the next step work?
The mate command uses distributed objects to talk to TextMate. Starting with 10.5 or 10.6 this is no longer supported from a shell session when there is no connection to the window server (AFAIK).
As a workaround you can alias ‘mate’ to ‘open -a TextMate’. It won’t be able to do -w though.
On Tue, Nov 16, 2010 at 18:01, Allan Odgaard mailinglist@textmate.org wrote:
On 16 Nov 2010, at 17:49, Justin Catterall wrote:
[...] The initial call to TM is working because TM activated. Any ideas how to make the next step work?
The mate command uses distributed objects to talk to TextMate. Starting with 10.5 or 10.6 this is no longer supported from a shell session when there is no connection to the window server (AFAIK).
As a workaround you can alias ‘mate’ to ‘open -a TextMate’. It won’t be able to do -w though.
Also, I seem to recall Apple patching the version of screen shipping with 10.5 and 10.6 to maintain this connection to the window server. If you built screen yourself or installed it with an external packaging system, you might want to try /usr/bin/screen instead.
Martin
On 16 Nov 2010, at 18:02, Martin Kühl wrote:
On Tue, Nov 16, 2010 at 18:01, Allan Odgaard mailinglist@textmate.org wrote:
On 16 Nov 2010, at 17:49, Justin Catterall wrote:
[...] The initial call to TM is working because TM activated. Any ideas how to make the next step work?
The mate command uses distributed objects to talk to TextMate. Starting with 10.5 or 10.6 this is no longer supported from a shell session when there is no connection to the window server (AFAIK).
As a workaround you can alias ‘mate’ to ‘open -a TextMate’. It won’t be able to do -w though.
Also, I seem to recall Apple patching the version of screen shipping with 10.5 and 10.6 to maintain this connection to the window server. If you built screen yourself or installed it with an external packaging system, you might want to try /usr/bin/screen instead.
I can make this work, and with 'open -a TextMate' and using -W, but the bash session is blocked until TextMate quits, not when it closes the file. Close, but no cigar. This is using /usr/bin/screen.
I'm just going to have to get used to more windows on my desktop.
On 2010-11-17 10:37, Justin Catterall wrote:
I'm just going to have to get used to more windows on my desktop.
FWIW, if you're running Leopard or newer, Terminal.app supports window tabs. You can thus have multiple shells in a single window, very similar to what you're doing with screen. You'll have to retrain your fingers, but if that's all you're using screen for it might be worth the effort.
I remember having this issue. The problem was that I used 'screen' from MacPorts. Apple's 'screen' (/usr/bin/screen) works fine with 'mate' since MacOS X 10.6. There is a description of this issue on the MacPorts bug tracker: https://trac.macports.org/ticket/18235
-Markus-
On 16 November 2010 19:02, Martin Kühl martin.kuehl@gmail.com wrote:
On Tue, Nov 16, 2010 at 18:01, Allan Odgaard mailinglist@textmate.org wrote:
On 16 Nov 2010, at 17:49, Justin Catterall wrote:
[...] The initial call to TM is working because TM activated. Any ideas how to make the next step work?
The mate command uses distributed objects to talk to TextMate. Starting with 10.5 or 10.6 this is no longer supported from a shell session when there is no connection to the window server (AFAIK).
As a workaround you can alias ‘mate’ to ‘open -a TextMate’. It won’t be able to do -w though.
Also, I seem to recall Apple patching the version of screen shipping with 10.5 and 10.6 to maintain this connection to the window server. If you built screen yourself or installed it with an external packaging system, you might want to try /usr/bin/screen instead.
Martin
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
On 17 Nov 2010, at 16:28, Markus Banfi wrote:
I remember having this issue. The problem was that I used 'screen' from MacPorts. Apple's 'screen' (/usr/bin/screen) works fine with 'mate' since MacOS X 10.6. There is a description of this issue on the MacPorts bug tracker: https://trac.macports.org/ticket/18235
-Markus-
There's the reason that it doesn't work for me, we're still on 10.5.8. Thank you for the reply.
Looks like I'll be going with Steve's suggestion of multiple tabs for now - I had forgotten that feature. I'll have to talk to the boss about up-grading the OS around the office - it's not like 10.6 is cutting edge any more.
-
Allan Odgaard -
Justin Catterall -
Markus Banfi -
Martin Kühl -
Steve King