Seems TM2 can only run one task at a time. I have multiple Xcode targets I run at the same time, TM2 only allows me to run one of them.
It also keeps reusing the same output window, so I can't have (for example) my ToDo list and view uncommitted changes at the same time.
Gerd
On 21 Dec 2011, at 01:38, Gerd Knops wrote:
Seems TM2 can only run one task at a time. I have multiple Xcode targets I run at the same time, TM2 only allows me to run one of them.
To get behavior similar to 1.x set: defaults write com.macromates.TextMate.preview htmlOutputPlacement window
Exactly how HTML output in splits should work is still surrounded by a few unknowns.
On Dec 21, 2011, at 4:09 AM, Allan Odgaard wrote:
On 21 Dec 2011, at 01:38, Gerd Knops wrote:
Seems TM2 can only run one task at a time. I have multiple Xcode targets I run at the same time, TM2 only allows me to run one of them.
To get behavior similar to 1.x set: defaults write com.macromates.TextMate.preview htmlOutputPlacement window
Already have this, and that is what I was talking about. Seems all commands then use the same window, instead of opening a new window.
Gerd
On 21.12.2011, at 11:09, Allan Odgaard wrote:
On 21 Dec 2011, at 01:38, Gerd Knops wrote:
Seems TM2 can only run one task at a time. I have multiple Xcode targets I run at the same time, TM2 only allows me to run one of them.
To get behavior similar to 1.x set: defaults write com.macromates.TextMate.preview htmlOutputPlacement window
Exactly how HTML output in splits should work is still surrounded by a few unknowns.
Hi Allan,
FYI if one sets htmlOutputPlacement to "window" it works but if one has let's say two Python or R scripts which I start after the other, i.e. both scripts are running then at the same time, only one HTML window will be used, not in that case two. In other words the second script overwrites the content of the HTML window. If I go back in that one HTML window I can see content of the first script but only to that point when the second was started.
I think it would be the best to just open a new HTML window for each script.
BTW The more I'm using TM2 (and I do it for weeks now exclusively) the more I like it :)
Cheers, --Hans
On Feb 4, 2012, at 9:49 AM, Hans-Jörg Bibiko wrote:
On 21.12.2011, at 11:09, Allan Odgaard wrote:
On 21 Dec 2011, at 01:38, Gerd Knops wrote:
Seems TM2 can only run one task at a time. I have multiple Xcode targets I run at the same time, TM2 only allows me to run one of them.
To get behavior similar to 1.x set: defaults write com.macromates.TextMate.preview htmlOutputPlacement window
Exactly how HTML output in splits should work is still surrounded by a few unknowns.
Hi Allan,
FYI if one sets htmlOutputPlacement to "window" it works but if one has let's say two Python or R scripts which I start after the other, i.e. both scripts are running then at the same time, only one HTML window will be used, not in that case two. In other words the second script overwrites the content of the HTML window. If I go back in that one HTML window I can see content of the first script but only to that point when the second was started.
I think it would be the best to just open a new HTML window for each script.
This bugged me enough to write an external app that sort of does this:
https://github.com/gknops/aplo.tmbundle
Here a sample bundle using it:
https://github.com/gknops/xcode4.tmbundle
I am hoping this is just a temporary solution, but given how much still needs to be done in TM2 it might not be that temporary at all.
BTW The more I'm using TM2 (and I do it for weeks now exclusively) the more I like it :)
I have used it exclusively since a few days after it came out. Some good ideas in it, but it has a long way to go to be what I hoped TM2 to be.
Sometimes I wish Allan would just concentrate on the editor view itself and provide a plugin system. So we could mold it to be what we want, and topics like project support or not, level of SCM integration etc. would all be moot, as we can just write our own!
Gerd
On 05/02/2012, at 00.46, Gerd Knops wrote:
[…] I am hoping this is just a temporary solution, but given how much still needs to be done in TM2 it might not be that temporary at all.
Right, and right.
BTW The more I'm using TM2 (and I do it for weeks now exclusively) the more I like it :)
I have used it exclusively since a few days after it came out. Some good ideas in it, but it has a long way to go to be what I hoped TM2 to be.
Sometimes I wish Allan would just concentrate on the editor view itself and provide a plugin system. So we could mold it to be what we want, and topics like project support or not, level of SCM integration etc. would all be moot, as we can just write our own!
Like Eclipse and emacs? :)
Seriously though, I don’t consider it sustainable to have me as the sole developer, but simply doing a plug-in interface is not exactly a good solution either (IMHO) — the various components of the app need to draw upon common infrastructure.
If you look in TextMate.app/Contents/Frameworks you’ll see that the app consists of several dozen frameworks. I think the most realistic approach to “opening up” is to open source some or all of these modules and/or the app which uses them.
I still have some infrastructure things I want to complete though; often a problem with open source is that no-one feels responsibility for refactoring or big infrastructural changes/improvements, most just do the minimal amount of work to scratch their itch (myself included, when I contribute to other’s projects), so I would like to reach a point with the code base where the foundation for most of the things I want to have in 2.0 has been laid.
I still have some infrastructure things I want to complete though[...], so I would like to reach a point with the code base where the foundation for most of the things I want to have in 2.0 has been laid.
So, you're announcing that TextMate will eventually be (at least partly) open-sourced?
On 14/02/2012, at 20.22, enas wrote:
So, you're announcing that TextMate will eventually be (at least partly) open-sourced?
I am not making announcements or committing to anything.
I am simply sharing my thoughts about long-term sustainability, interpret these as you want, but don’t expect me to try and predict the future, there are far too many unknown variables.
I am not making announcements or committing to anything.
Don't worry, I was just teasing you :) It's just that when I was reading Gerd asking for a plugin system, I thought "what plugin system, open-source it altogether" (if we are to be making wishes, that is). So I was happy to see that you're more on this side of the "argument".
I am simply sharing my thoughts about long-term sustainability, interpret these as you want,
I do indeed interpret them as I want. And what I notice, is that you seem to have made quite some elaborate plans to, at least, leave this option feasible :) But that's just me sharing my impressions.
-
Allan Odgaard -
enas -
Gerd Knops -
Hans-Jörg Bibiko