(5)
Your rating: Now say why...
OpenTerminal opens the Terminal with cd command.
When you are working in the Finder and you discover that you need a terminal window you have to open "Terminal" and "cd" to the folder you were working on. With OpenTerminal you just click its icon or use the Finder's contextual menu and a terminal with the correct path shows up.
The advantage of OpenTerminal over other available tools is that it can run in the background (without using processor time) and react instantly because it doesn't have to start up first. It's also more refined than the other tools I know of: it
When you are working in the Finder and you discover that you need a terminal window you have to open "Terminal" and "cd" to the folder you were working on. With OpenTerminal you just click its icon or use the Finder's contextual menu and a terminal with the correct path shows up.
The advantage of OpenTerminal over other available tools is that it can run in the background (without using processor time) and react instantly because it doesn't have to start up first. It's also more refined than the other tools I know of: it
What's New
Version 2.07:
- Works better with Mac OS X's Spaces feature
- Includes some new workarounds for iTerm bugs
- The alternative icon for the Finder's toolbar has been updated so it's no longer misaligned.
- Works better with Visor (added in 2.06b)
Requirements
- Intel
- Mac OS X 10.6 or later.
- iTerm support has been tested with version 0.10
OpenTerminal User Discussion (Write a Review)
Overall:
(5)
(5)
Displaying 1-10 of 12
-
-
-
OpenTerminal opens the Terminal with cd command.
When you are working in the Finder and you discover that you need a terminal window you have to open "Terminal" and "cd" to the folder you were working on. With OpenTerminal you just click its icon or use the Finder's contextual menu and a terminal with the correct path shows up.
The advantage of OpenTerminal over other available tools is that it can run in the background (without using processor time) and react instantly because it doesn't have to start up first. It's also more refined than the other tools I know of: it includes workarounds for several Finder and Terminal bugs, supports Spaces, and it doesn't open superfluous terminal windows.
The sourcecode is also available.
When you are working in the Finder and you discover that you need a terminal window you have to open "Terminal" and "cd" to the folder you were working on. With OpenTerminal you just click its icon or use the Finder's contextual menu and a terminal with the correct path shows up.
The advantage of OpenTerminal over other available tools is that it can run in the background (without using processor time) and react instantly because it doesn't have to start up first. It's also more refined than the other tools I know of: it includes workarounds for several Finder and Terminal bugs, supports Spaces, and it doesn't open superfluous terminal windows.
The sourcecode is also available.
Copyright © 2012 MacUpdate LLC
- -
+14
Jichi reviewed on 04 Jan 2012
However, after switched to iTerm2 from iTerm, I found OpenTerminal didn't work with iTerm2. Wish the developer add the support for iTerm2 as well.
I used this app with iKey and mapped MAC+F1 to open iTerm here which saved me lot of time. I would definitely purchase this app if it goes on AppStore. Anyway, thx a lot for the developer for his work.
+1
+79
Thanks for the "cdf" idea. But the script failed to work when the pathname contains white spaces. I've tweaked the script for a work-around:
alias cdf="eval "cd \"\`osascript -e 'tell app \\\"Finder\\\" to return the POSIX path of (target of window 1 as alias)'\`\"""
Adding this line to ~/.bashrc, and every terminal environment could "cdf" to the directory of the frontmost Finder window.
+79
All the backslashes showed up there shall be doubled:
alias cdf="eval \"cd \\\"\\\`osascript -e 'tell app \\\\\\\"Finder\\\\\\\" to return the POSIX path of (target of window 1 as alias)'\\\`\\\"\""
+79
Thanks for the "cdf" idea. But the script failed to work when the pathname contains white spaces. I've tweaked the script for a work-around:
alias cdf="eval "cd \"\`osascript -e 'tell app \\\"Finder\\\" to return the POSIX path of (target of window 1 as alias)'\`\"""
Adding this line to ~/.bashrc, and every terminal environment could "cdf" to the directory of the frontmost Finder window.
+2
+1
+53
Crunc reviewed on 29 Jul 2010
+4
If you find another bug, please e-mail me directly and I'll try to help more quickly. (You can find my e-mail address at the bottom of the readme file.)
+1
TexLogic reviewed on 25 Jan 2008
+10
I have added your instructions to the OpenTerminal readme file. I've slightly modified them to work with OpenTerminal, so that "cdf" can use OpenTerminals functionality (support for Unicode file names, cd to the desktop if no windows are open, cd to the trash folder, etc.)
An especially cool thing with your command is that it works with every terminal application including xterm.
+46
####################################################################
# implement cdf command #
# (changes the working dir to the front-most window of the Finder) #
####################################################################
cdf()
{
eval cd "`osascript -e 'tell app "Finder" to return the quoted form of the POSIX path of (target of window 1 as alias)' 2>/dev/null`"
}
With this added to your .bashrc file, you can open a terminal window and type "cdf" to change the working directory to the front-most Finder window.
-8
cdf()
{
open .
}
;)
+46
+53
If it still doesn't work, please e-mail me.
+53
Just redownload OpenTerminal and e-mail me if it doesn't work.
+53
+3
+3
+3
Kuean rated on 19 Dec 2010