Hmm, don't know much about apple script and whats avail in Terminal,
but just opened the Dictionary for the Terminal and it has
window n
.name
.processes
etc..
so you could either set the name before you start fsch the first
time, then you'd be able to find it and run the commands.
To be able to run within TM, I have never seen any other bundle
reusing a running instance of some app, but one way would be to use a
local socket and make the communication between the nice TM-window
and the running terminal app.
The output from the running fsch, either wrap it and grab the std out/
err or pipe the output to some temp-file which the TM-window could
read from
Anyone got hints on other bundes doing such things with TM !?
On May 29, 2007, at 11:08 AM, Simon Gregory wrote:
Any reason why iTerm is required for the build fcsh shell script?!
I was thinking the same thing… at least it should be Terminal with
an optional use of iTerm.
[....]
Simon, is there any need for the interactive features of the terminal
when doing the build? Or could this run as a TM command?
As iTerm has better applescript support I'm afraid it is the only
solution.
This is because Terminal can't target a specific window and
virtually type
into it, and unfortunately when fsch has been started this is the
only way
to interact with it. I know this is a hacked solution, and I'd love
to be
able to launch an interactive deamon instance of fsch to interact with
and feed the results back to a TM html window but the functionality
isn't
there. Using fsch in this way is worth it as it is so much faster than
launching mxmlc (the as3/flex compiler) directly, to the best of my
knowledge this is because it is caching the build in RAM.
If anyone has any suggestions on interacting with running processes
then I'm all ears as I'd love to see a more elegant solution.
_______________________________________________
textmate-dev mailing list
[email protected]
http://lists.macromates.com/mailman/listinfo/textmate-dev
