English | OpenInTerminal 中文说明
How to use
|Open X (e.g., folders or files) in Terminal or Editor|
|Open the selected in X (e.g., Github Desktop)|
|Features||OpenInTerminal||OpenInTerminal-Lite & OpenInEditor-Lite|
|Support Terminal, iTerm, Hyper, Alacritty and kitty.||
|Support TextEdit, Visual Studio Code, VSCode Insiders, Atom, Sublime Text, VSCodium, BBEdit, TextMate, CotEditor, MacVim and JetBrains(AppCode, CLion, GoLand, IntelliJ IDEA, PhpStorm, PyCharm, RubyMine, WebStorm).||
|Open in custom apps. (
|Support English, Chinese, French, Russian, Italian and Spanish.||
|Support keyboard shortcuts.||
OpenInTerminal and OpenInTerminal-Lite (OpenInEditor-Lite)
Which one to choose? Both of these apps are my children. If you like more powerful features and GUI preferences, then you can use
OpenInTerminal. If you just need to open terminal faster and more stably, then you can use
For me, I prefer
OpenInTerminal-Lite which only needs to click once to complete the function (and the other needs to click twice
How to install
brew install --cask openinterminal
Download from release.
Move the app into
⚠️macOS will ask your permissions to access Finder and other applications when you run the app for the first time. Please give OpenInTerminal the permissions.
2. Check Finder Extension permission
Open the OpenInTerminal app. Go to
System Preferences ->
Finder Extensions, check the permission button as below.
If you have a good idea, feel welcome to open a new issue.
Thank you for your support!
1. What is the difference between OpenInTerminal and OpenInTerminal-Lite?
OpenInTerminal currently has a normal version and a lite version. If you like more powerful features and GUI preferences, then you can use OpenInTerminal. If you just need to open terminal faster and more stably, then you can use OpenInTerminal-Lite.
2. I accidentally clicked on the
Don't Allow button.
You can run the following command in the terminal. This will reset the permissions in the System Preferences.
tccutil reset AppleEvents wang.jianing.app.OpenInTerminal
3. Special characters in the
Please do not use backslash
\ and double quotes
" in the path.
4. Open two Terminal windows on Mojave
This problem usually occurs when Terminal is first started. So you can use
⌘W to close Terminal window instead of using
⌘Q to quit Terminal.
5. OpenInTerminal Finder extension doesn't work.
Currently Finder extension is completely dependent on AppleScript in order to run independently. So it is hard to guarantee its stability. When you find that Finder extension doesn't work properly, you need to hold down the
Option(⌥) key, right-click on Finder, and select
If your Mac model is a bit old like mine, I suggest you cancel the icon in the context menu in Preferences. If it still crashes frequently, it is recommended to use OpenInTerminal-Lite.
6. OpenInTerminal doesn't work as I expected
OpenInTerminal will open terminal or editor as the following order:
- 1. Open the file or folder that you selected.
- 2. Open the top Finder window.
- 3. Neither. Then open the desktop.
For example, if you select a file in the bottom Finder window and you want to open the above Finder window in terminal, this will not work as you expected according to the above order.
Q: I right-click on the desktop but no terminal or editor appears. But actions in status bar menu work.
A: Try to select a file(folder) or open a Finder window. Because when you right-click on the desktop and nothing is selected, system does not provide program with the path of selected files. Under this situation, the program does not work.
Currently they(Fidner extension and actions in status bar menu) do not work as the same way. Finder extension is completely dependent on AppleScript in order to run independently, while status bar icon works as before. So they have different behaviors. This problem will be improved in the future.
7. The implementation mechanism of OpenInTerminal and why there are two versions.
There are two ways to achieve "open in terminal".
- 1. ScriptingBridge. It's faster and more stable than the second one, although the differences are small.
OpenInTerminal-Liteand actions of
OpenInTerminalin status bar menu are based on this way. Its disadvantage is that applications which use ScriptingBridge to access user's directory infomation or something else cannot be sandboxed.
- 2. AppleScript. Finder extension of
OpenInTerminalis completely dependent on AppleScript in order to run independently. The first way cannot be applied to Finder extension because it is required to be sandboxed.
Some people want OpenInTerminal to be fast and stable(the lite version), while others want OpenInTerminal to be powerful and easier to configure(the normal version). Some people hope that OpenInTerminal can automatically adapt to dark mode(the normal version), while others just want to open the terminal with one click(the lite version).
When one version can no longer meet these needs, OpenInTerminal was split into a normal version and a lite version a few months ago.
(BTW, I know there are apps that are sandboxed and can achieve the same effect as OpenInTerminal. But I don't know how it implements this. If anyone knows it and is willing to talk to me, that would be great. I'm very happy to make OpenInTerminal more perfect so that one version is enough.
8. My custom app doesn't work.
If your custom application cannot work by running the following command, then the application cannot be supported. For example, GitHub Desktop:
open -a GitHub\ Desktop ~/Desktop
- Fix: cannot open path with white space when using shortcut
- Fix: cannot open path with white space
- Fix: cannot open alacritty
- Feat: add quit button in preferences
- Open custom apps. (Not all apps support)
- Show icon in context menu. (For stability, old Mac models are not recommended to display icons)
- Support kitty
- Open multi-selected files in editors
- Support Italian and Spanish
- Fix: does not show Terminal and TextEdit
- Support JetBrains
- Fix: check whether an application exists
- Custom Finder menu options
- Support Russian
- Support PhpStorm
- Fix: doesn't work when opening desktop in terminal
- Signed the application with the developer account. Bundle ID has changed
- Support Finder Extension Standalone Operation Mode
- Support CotEditor and MacVim
- User can hide context menu items
- Finder context menu item's title will change to the current default terminal or editor
- Fix: check application exist bug
- Support TextMate
- Fix: keyboard shortcut bug
- Fix: Finder context menu icon supports dark mode
- Support Visual Studio Code - Insiders
- Support for hiding the status bar icon
- Support BBEdit
- Add icon in Finder context menu
- Fix: check application folder under home directory
- Fix: Finder context menu does not appear on other disks.
- iTerm will not leave `cd xxx` in history.
- You need to click the `window` button or the `tab` button of iTerm again in `Preferences`.
- Support keyboard shortcuts.
- Support VSCodium.
- Support French.
- OpenInTerminal has been released after several weeks of development. If you have suggestions or there are bugs, please feel free to open an issue.
- You can set a default to open a new tab or window when using
- Change name to
OpenInTerminalwill come as a more powerful version in the future.)
- Fix a bug that some special characters in the path would crash the program when opening Hyper.
- Add terminal selector
- Cancel running
clearcommand when opening iTerm
- Give priority to creating a new tab when opening iTerm
- First release
Special Thanks to
Thanks to all contributors. Your work makes OpenInTerminal better.