iTerm2 and Path Finder 7 integration not working

Path Finder 7 (PF7) has an option to set a custom terminal to launch when using 'Open in terminal' function to open a terminal window and 'cd' to the current folder in PF7. I've set my custom terminal to iTerm2. However, this integration is not working. There are already multiple support tickets in PF7

http://support.cocoatech.com/discussions/problems/32137-open-in-terminal-doesnt-work-for-iterm2 http://support.cocoatech.com/discussions/problems/12248-open-in-terminal-does-not-work-with-iterm2 http://support.cocoatech.com/discussions/problems/26227-path-finder-7-cannot-open-iterm-2 http://support.cocoatech.com/discussions/problems/31988-iterm-not-working-from-toolbar-button http://support.cocoatech.com/discussions/problems/32182-open-in-iterm-not-working

Since I'm using a beta build, PF7 wouldn't really help much — they'll just point out to use a stable build. Also, I don't really know if that's something iTerm2 can fix or only PF7 (I'm assuming iTerm2 since default Mac terminal is working fine and from what I understand other versions of iTerm2 are working fine). So I would just like to draw your attention to this bug, and hope that you find why it happens and take it into account in developing new versions of iTerm2. These two replacements of the stock apps are just too awesome and should work together happily :)

System info:

Path Finder 7: 7.2.1/1692

iTerm2: Build 2.9.20151001

OS X: OS X 10.11.1 (15B42)

Attached files

1. plist com.googlecode.iterm2.plist

2. Debug log (tried to use 'Open in terminal' function in PF7, but not sure whether iTerm2 debug tool caught that command) debuglog.txt.zip

Sorry, I had to break applescript compatibility in 2.9. I'll get in touch with them and see what I can do to help.

Ok, thanks for a prompt response. Please kindly do coordinate with them on how this issue can be resolved — your app and PF are two of my favorite utilities on OS X!

Hello -- I was wondering if there has been any progress along these lines, i.e. getting applescript back to a functional state with respect to Path Finder. I miss the terminal integration with Path Finder but do not want to switch back to a much earlier release of iTerm2 either. Thanks, and I'm very appreciative to both teams and individuals for these (2) awesome products. =bwh=

I reached out to the Pathfinder team on Twitter but they weren't responsive. I recommend letting them know you're interested in this, and maybe that will help bump up its priority.

@gnachman, would you please at least email them? Twitter doesn't seem a reliable medium for this. As far as I understand, they don't even know the problem exists, e.g. a two-months old ticket (http://support.cocoatech.com/discussions/problems/37072-pathfinder-doesnt-open-iterm2) got closed because "it works absolutely fine". Now, how can it work "absolutely fine" if you say yourself you broke applescript compatibility?

Meanwhile, @bruiiser, I've found a workaround by using Alfred 2 and its awesome workflow "Terminal Finder 1.6.0", where ⇪+ft (⇪ in my case opens Alfred 2, mapped through Karabiner) would open the folder in iTerm2. I still miss a bit the convenience of a context menu, but this is rather minor now.

Well, they did respond, but they referred to a licensing disagreement from a few years ago and then stopped answering. They don't seem to be interested in supporting beta versions based on the issue comment.

My plan is to exit beta and then maybe there will be enough pressure for them to catch up. I can understand them not wanting to support two different versions, but I wish they'd get ahead of this for the sake of their users.

@gnachman I'm all up for not calling your awesome app beta, doesn't look like beta to me ;) Would you kindly reach out to them once you exit beta? I'm up to writing an additional ticket at Path Finder 7 forums. Meanwhile, I'm still confused by their last ticket where "it works absolutely fine". Would you please confirm that it's actually still not working (if you have PF7)? Thank you

Milestone changed to Ship 3.0

See release notes for Path Finder 7.3.3 on http://support.cocoatech.com/kb/installation-and-compatibility/path-finder-version-history .

Does 7.3.3 work for you @wagnerand ? I set it up like this:

But if I right-click on a folder in Path Finder and choose Open in Terminal it still opens in Terminal.app.

The integration works for me with the 7.3.3 (1700) release of Path Finder and the lastest nightly release of iTerm2 (iTerm2-2_9_20160519-nightly). In fact this has been the case ever since Path Finder announced the compatibility changes, and I update iTerm2 with nightly builds every other week mostly. Now I do not have all the optins selected like those in the screen shot above, and the iTerm2 application out of the zipped bundle from the git download is by default named 'iTerm.app'. You may have renamed it I don't know ... but I'm presuming if you have the proper version of iTerm selected then the configuration at least should be correct.

I am very happy! Hope you find your issues ...

=bwh=

Doesn't work for me either. I have PathFinder 7.3.3 and iTerm2 Build 2.9.20160523 and set it as default terminal in PathFinder per screenshot above (one difference, though, is the name of the app I have is iTerm, not iTerm2)

Also, I don't have a Terminal.app opening a folder when I set default terminal as iTerm, nothing happens at all. If I set default terminal as Terminal.app then Terminal.app opens at the location specified with Open in Terminal command.

@eugenesv Please get in touch with PathFinder support and let them know there's an issue.

@gnachman trying to troubleshoot a separate issue I've reinstalled PF from scratch (removing old pref files, caches and everything) and it's finally working! No clue what was wrong (and after restoring plist settings it didn't come back). Thanks!

Status changed to closed