Skip to content

Latest commit

 

History

History
126 lines (90 loc) · 4.98 KB

README-Config.md

File metadata and controls

126 lines (90 loc) · 4.98 KB

OpenInTerminal Configurations

Finder Extension Configuration

To enable Finder Extension, right click on Finder toolbar, select Customize Toolbar... as shown below:

Then drag the OpenInTerminal icon to the toolbar:

Finder Extension Not Showing Up in System Settings on macOS 15

1) Manually Enable the Finder Extension

Starting with macOS 15, Apple removed the Finder Sync Extension configuration from System Settings. To enable the Finder Extension, use the pluginkit command-line tool as follows:

$ pluginkit -mAD -p com.apple.FinderSync -vvv

You should see output similar to the following:

wang.jianing.app.OpenInTerminal.OpenInTerminalFinderExtension(2.3.5)
           Path = /Applications/OpenInTerminal.app/Contents/PlugIns/OpenInTerminalFinderExtension.appex
           UUID = F2547F13-4E43-4E88-9D8F-56DF05C020D8
      Timestamp = 2024-09-17 09:34:07 +0000
            SDK = com.apple.FinderSync
  Parent Bundle = /Applications/OpenInTerminal.app
   Display Name = OpenInTerminalFinderExtension
     Short Name = OpenInTerminalFinderExtension
    Parent Name = OpenInTerminal
       Platform = macOS

To manually enable the Finder Extension, run the following command with the UUID from the output:

$ pluginkit -e "use" -u "F2547F13-4E43-4E88-9D8F-56DF05C020D8"

2) Use FinderSyncer

Alternatively, you could use a GUI tool called FinderSyncer to enable the extension.

Checking Finder Extension Permissions on macOS 14 and Earlier

For macOS 14 and earlier, ensure the Finder Extension is enabled via System Preferences:

  1. Open the OpenInTerminal app.
  2. Navigate to System Preferences -> Extensions -> Finder Extensions.
  3. Check the checkbox next to OpenInTerminalFinderExtension, as shown below:

Custom Configuration

For Neovim Users

If you select Neovim as your editor in OpenInTerminal, the app will use Kitty as the default terminal. To switch to a different terminal (supported options: Alacritty, WezTerm, and Kitty), update the configuration with the following command. Replace <Your Name> with your username and adjust the Neovim path (/opt/homebrew/bin/nvim in this example) to match your installation:

defaults write /Users/<Your Name>/Library/Group\ Containers/group.wang.jianing.app.OpenInTerminal/Library/Preferences/group.wang.jianing.app.OpenInTerminal.plist NeovimCommand "open -na wezterm --args start /opt/homebrew/bin/nvim PATH"

Other terminal configurations:

// kitty:
"open -na kitty --args /opt/homebrew/bin/nvim PATH"
// WezTerm:
"open -na wezterm --args start /opt/homebrew/bin/nvim PATH"
// Alacritty:
"open -na Alacritty --args -e /opt/homebrew/bin/nvim PATH"

For Kitty Users

The default launch behavior for kitty is to open a new instance for each command, like the following:

open -na kitty --args --single-instance --instance-group 1 --directory

If you want to customize this behavior, you can run the following command in your terminal. Make sure to replace <Your Name> with your username and adjust the open command as what you want:

defaults write /Users/<Your Name>/Library/Group\ Containers/group.wang.jianing.app.OpenInTerminal/Library/Preferences/group.wang.jianing.app.OpenInTerminal.plist KittyCommand "open -na kitty --args --single-instance --instance-group 1 --directory"

FAQ ❓

Oops, hit Don't Allow button by mistake.

No sweat! Just run the following command in your terminal, and it'll reset the permissions in System Preferences.


tccutil reset AppleEvents wang.jianing.app.OpenInTerminal
Special characters in the path.

Please do not use backslash \ and double quotes " in the path.

Open two Terminal windows on Mojave

This problem usually occurs when you first start Terminal. Try using ⌘W to close Terminal window, instead of using ⌘Q to quit Terminal.

OpenInTerminal doesn't work as I expected

OpenInTerminal works as the following order:

  • 1. Open the file or folder you selected.
  • 2. If nothing's selected, it opens the top Finder window.
  • 3. If there's no Finder window, it opens the desktop.
My custom app doesn't work.

If your custom application doesn't work with the following command, then it's not supported. For example, GitHub Desktop:

open -a GitHub\ Desktop ~/Desktop