Please follow the instruction and check if the issue still persists:
Make sure that Path Finder is located in the Applications folder
Open your terminal and paste the following command to check if Path Finder has been slapped with the quarantined extended attribute:
xattr /Applications/"Path Finder.app"
If you see com.apple.quarantine returned as output from that last command, then go ahead and run this next command:
xattr -d com.apple.quarantine /Applications/"Path Finder.app"
You won't get any feedback or output from that command, but that's okay because you can just run the first command again to see for yourself if the com.apple.quarantine attribute shows up again. It shouldn't, and now Path Finder is freed from Apple quarantine jail. Restart your PathFinder now.
Don't hesitate to contact us should any questions arise.
The terminal based suggestion revealed, via xattr, that PF has not been "slapped with the quarantined extended attribute," as was suggested as a possibility. After running xattr as directed, after a brief pause, a new prompt appears with nothing else. So I'm still left with a non-functioning Terminal module, as well as a non-functioning file compare, which I've written about before, and elsewhere today. It's tempting to think staff is so swamped with trying to get this "beta release" up to speed that many things are not being addressed. I'd like to have you chime in on this and disabuse me of the thought . . .
Jordan . . .
Nothing changed regarding the failure of the Terminal module to complete its link up to bash. Same as before. Useless.
What did change, and how aggravating!, is that all the modifications I've made, the fonts and browser window appearance, a couple of different saved/named sidebars, a few other things I'm sure that I haven't found yet, are gone, kaput.
You've got an angry client base here, some of whom have given up on PF, and I find it easy to understand why.
PF 8.2: The uselessness of the Terminal module has not been fixed in this upgrade. Just to let you know. That's not a fatal flaw, but added to all the others leads one to pessimism that this mess will ever be cleaned up.
In PF 8.3.6 the uselessness of the Terminal module has not been addressed; it still does not complete a link up to bash. The terminal module shows up but has not connected to bash. Still. Any hope of getting this to work?
Sure, I can have the default be terminal.app and be able to jump out to
terminal from PF. But neither doing that nor having PF be the default
terminal allows the PF Terminal Module to work. That's the issue.
It's time for me to bring this topic up again; the Terminal Module hangs without getting to the BASH prompt. The file uploaded on Aug 22 of last year still precisely applies, showing the hung module. It does not accept keystrokes. I should make clear that I'm not talking about evoking "Show in terminal", which works (once I've given iTerm permission to connect to PF). It is the Modular variety that does not work (on my system at least, which is a pretty standard Mac OS 10.14.3.) Nor does it matter if General->Terminal->Default Terminal is set to the native OS or iTerm in Preferences.
Another "ping" to the developers, I guess.
> If you select Path Finder terminal as the default terminal, will it work
> when not added as a module?
It loads up to the point the module version does. Like in the module
example, it accepts no keystrokes. It seems to load bash and the *top *command
I put in preferences, but it accepts no keyboard or mouse input. I've
attached a screenshot.
Later on Preferences can be restored if you have a copy of the following items:
/Library/Application Support/Path Finder/ (folder) /Users/your username here/Library/Application Support/Path Finder/ (folder) /Users/your username here/Library/Preferences/com.cocoatech.pathfinder.plist (file)
However, please do not restore them immediately after reinstall and test the Terminal first.
Then you may quit Path Finder, delete the new items above and copy back originals, and relaunch the app.
Please feel free to write us back and we will be happy to assist you.
I did all that you suggested, without changing a thing regarding use of the
Terminal Module. I did lose all modifications; when I replaced the
configuration files with the ones I'd copied from the old system, I got
some of the mods back, not all.
I'm seeing the same problem with the terminal not working. In my case, the pathfinder terminal doesn't seem to be compatible with the iterm2 shell integration scripts called from my .zshrc file. I had to wrap the script calls inside a test to get it to work correctly.