i keep a folder of saved terminals (*.term files) which i use to open color-coded terminals (blue.term, red.term, green.term, etc).
after using the CTRL-SHIFT-o from textmate to open a terminal at the current files directory, double-clicking my .term files in finder no longer opens a terminal, until i close all terminals and re-open Terminal.app, then the *.term files work again until i next CTRL- SHIFT-o from textmate.
On 17/7/2006, at 21:02, Michael Reece wrote:
i keep a folder of saved terminals (*.term files) which i use to open color-coded terminals (blue.term, red.term, green.term, etc).
after using the CTRL-SHIFT-o from textmate to open a terminal at the current files directory, double-clicking my .term files in finder no longer opens a terminal, until i close all terminals and re-open Terminal.app, then the *.term files work again until i next CTRL-SHIFT-o from textmate.
I don’t think the problem is with TextMate. The Open Terminal (⌃⇧O) just asks Terminal for a new window and instructs it to CD to the directory of the current document.
There have been two cases in the past where this caused the users Terminal preferences to somehow record that in the future Terminal should CD to that folder as part of its startup (or similar.) Though I haven’t been able to reproduce it, and TextMate doesn’t do anything special in the Open Terminal command (you can have a look at the code in the bundle editor.)
weird. i get the same behavior/problem on my mac at home. double-clicking .term files no longer works after doing open-terminal from textmate.
does it not cause that problem for others? maybe it is a bug with terminal ..
On 17/7/2006, at 21:02, Michael Reece wrote:
i keep a folder of saved terminals (*.term files) which i use to open color-coded terminals (blue.term, red.term, green.term, etc).
after using the CTRL-SHIFT-o from textmate to open a terminal at the current files directory, double-clicking my .term files in finder no longer opens a terminal, until i close all terminals and re-open Terminal.app, then the *.term files work again until i next CTRL-SHIFT-o from textmate.
I donât think the problem is with TextMate. The Open Terminal (ââ§O) just asks Terminal for a new window and instructs it to CD to the directory of the current document.
There have been two cases in the past where this caused the users Terminal preferences to somehow record that in the future Terminal should CD to that folder as part of its startup (or similar.) Though I havenât been able to reproduce it, and TextMate doesnât do anything special in the Open Terminal command (you can have a look at the code in the bundle editor.)
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Jul 18, 2006, at 12:16 PM, mreece@vinq.com wrote:
weird. i get the same behavior/problem on my mac at home. double-clicking .term files no longer works after doing open- terminal from textmate.
does it not cause that problem for others? maybe it is a bug with terminal ..
It is Terminal.app. I ran into similar problems trying to use AppleScript to do somethings with terminal, and ended up filing a bug with Apple. Please do the same so they realize its a PITA for users out here :)
-pete
On Jul 18, 2006, at 2:15 AM, Allan Odgaard wrote:
On 17/7/2006, at 21:02, Michael Reece wrote:
i keep a folder of saved terminals (*.term files) which i use to open color-coded terminals (blue.term, red.term, green.term, etc).
after using the CTRL-SHIFT-o from textmate to open a terminal at the current files directory, double-clicking my .term files in finder no longer opens a terminal, until i close all terminals and re-open Terminal.app, then the *.term files work again until i next CTRL-SHIFT-o from textmate.
I don’t think the problem is with TextMate. The Open Terminal (⌃⇧O) just asks Terminal for a new window and instructs it to CD to the directory of the current document.
It's a Terminal problem. It's supposed to be some sort of virus protection thing, but it's extremely poorly implemented IMHO.
There have been two cases in the past where this caused the users Terminal preferences to somehow record that in the future Terminal should CD to that folder as part of its startup (or similar.) Though I haven’t been able to reproduce it, and TextMate doesn’t do anything special in the Open Terminal command (you can have a look at the code in the bundle editor.)
That is caused by hitting the Use Setting as Defaults button in the Window Settings inspector.
thomas Aylott—subtleGradient
-
Allan Odgaard -
Michael Reece -
mreece＠vinq.com
-
peter royal -
thomas Aylott