Terminal Plugin Issues

[bwaang]

In the latest 2.3.0, whatever changes were made has broke the following - these seem to be regressions as they were working in the previous version. (Also in the meantime is there a possible way to have older Terminal plugin available, this is hindering a lot of automation that I do on my machine... it would help greatly if I could revert to an older version)

• Executable shell files (chmod +x) that do not have a specific extension is not recognized by the plugin as a runnable files, thus Run [...] or Run in Terminal [...] does not show up as valid actions anymore - files need to have explicit (e.g. *.sh) extension it seems, which is not the case for any of the built in Terminal commands.

• Executing scripts that require arguments no longer works, it seems to be executing the scripts without any arguments even if I supply arguments in the third pane.

• The *.scpt files, Apple Script files no longer have AppleScript Editor as a valid action, even though AppleScript Editor application still exists on the system

Thank you for continuing development on this product, but I would hate to see things get worse and less useable as development continues, especially regressions would be the most tragic thing to see when things stop working as it once did.

[pjrobertson]

Thanks for reporting this.
The first issue appears to be a problem in QS not the plugin, and is probably the cause of the other problems. We'll have to fix the app before this will start working again. In the meantime you can downgrade to the previous version:
http://cdn.qsapp.com/com.blacktree.Quicksilver.QSSpotlightPlugIn__236.qspkg

[bwaang]

Thanks for the reply, downgrading to ß70 seemed to help some issues above, but now the Run [...] doesn't seem to be bringing up the third pane to take in arguments anymore, this installed in conjunction with the 2.3.0 Terminal Plugin. Also Run with Arguments is not an available action.

This issue seems to be something with the Terminal Plugin specifically as I downgraded all the way down to ß54 and the issue still persists.

[pjrobertson]

yes, the issue is intertwined in both the plugin and the app, when we
update the app (hopefully in the next week or so) there should be a fix for
this in it. But you can downgrade the plugin to get things working now

On 20 March 2013 01:21, bwaang notifications@github.com wrote:

Thanks for the reply, downgrading to ß70 seemed to help some issues above,
but now the Run [...] doesn't seem to be bringing up the third pane to take
in arguments anymore, this installed in conjunction with the 2.3.0 Terminal
Plugin:

[image: no-arguments-1]https://f.cloud.github.com/assets/3912116/277296/c4ef41ba-90c1-11e2-9dec-2971b6147221.png
[image: no-arguments-2]https://f.cloud.github.com/assets/3912116/277297/c90f346c-90c1-11e2-9717-ac3373d6ab9a.png

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1427#issuecomment-15133453
.

[bwaang]

Thanks for looking into this and the update. But that's the thing I haven't figured out what to do, how do you downgrade the plugin, I haven't found an option or an repository with any of older revisions of the Terminal Plugin or any QS plugin for that matter. Could you advise, thanks!

FYI, the link that you provided was for the Spotlight Plugin and not the Terminal Plugin - now looking at it, I'm guessing that was what you were trying to provide me.

[pjrobertson]

Use the link I provided above to download the plugin. Then remove the newer plugin from ~/Library/Application Support/Quicksilver/PlugIns and double click the new downloaded file

[bwaang]

Oh the link that you gave above seems to be for the QSSpotlightPlugIn, looking for the older version of the QSTerminalPlugin, thanks.

[pjrobertson]

Woops apologies,

Try: http://cdn.qsapp.com/com.blacktree.Quicksilver.QSTerminalPlugIn__313.qspkg

[bwaang]

Thanks it works!

[pjrobertson]

This is fixed in later versions of Quicksilver. Thanks!