Is it possible? It seems that whatever name I give to either of the apps (eg. renaming one to "TextMate2"), when I start TextMate2 it appears to be loading (bouncing in the Dock) and then vanishes and focus is put to TextMate1, which is already open.
Running just one of the versions works.
- Matthias
On 14 Dec 2011, at 07:06, Matthias wrote:
Is it possible? It seems that whatever name I give to either of the apps (eg. renaming one to "TextMate2"), when I start TextMate2 it appears to be loading (bouncing in the Dock) and then vanishes and focus is put to TextMate1, which is already open.
They should run in parallel _without_ renaming them.
They don't run in parallel, I have the same problem.
On Wed, Dec 14, 2011 at 1:38 AM, Allan Odgaard mailinglist@textmate.org wrote:
On 14 Dec 2011, at 07:06, Matthias wrote:
Is it possible? It seems that whatever name I give to either of the apps (eg. renaming one to "TextMate2"), when I start TextMate2 it appears to be loading (bouncing in the Dock) and then vanishes and focus is put to TextMate1, which is already open.
They should run in parallel _without_ renaming them.
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Am 14.12.2011 um 10:38 schrieb Allan Odgaard:
On 14 Dec 2011, at 07:06, Matthias wrote:
Is it possible? It seems that whatever name I give to either of the apps (eg. renaming one to "TextMate2"), when I start TextMate2 it appears to be loading (bouncing in the Dock) and then vanishes and focus is put to TextMate1, which is already open.
They should run in parallel _without_ renaming them.
I'm also unable to start both in parallel. (OSX 10.6.8) Separately it seems to work smoothly.
just my 2 ct.
The problem is that both versions detects that TM is running already without checking the version, so it activates the running one instead of launching its own. Anyway what's the purpose of running them in parallel? ;)
The problem is that both versions detects that TM is running already without checking the version, so it activates the running one instead of launching its own. Anyway what's the purpose of running them in parallel? ;)
That's the behavior I'm seeing. I would like to run in parallel to play with the new version but still be able to continue doing production work with 1.5...
On Dec 14, 2011, at 5:42 AM, Matthew Johnson wrote:
The problem is that both versions detects that TM is running already without checking the version, so it activates the running one instead of launching its own. Anyway what's the purpose of running them in parallel? ;)
That's the behavior I'm seeing. I would like to run in parallel to play with the new version but still be able to continue doing production work with 1.5...
I'm seeing the not-able-to-run-both-at-once behavior, as well. I agree with the sentiment that I don't think it's very good idea to do real work for real paying clients while using alpha software. At any rate, none of my custom bundles or bundle customizations seems to have made their way into TM2, so I'm MUCH more productive in TM 1 at this point. Yet I'd like to have TM 2 open to get a feel for it and possibly help out by reporting issues.
-
Adam Strzelecki -
alex kessinger -
Allan Odgaard -
Dru Kepple -
Matthew Johnson -
Matthias -
Patric Zimmermann