According to the screenshot, the action inside the loop is not a default KM action. This is a custom action written by a user, who happens to be me (“Execute a Script in Terminal”).
It would probably be possible to close the Terminal window after successful exit (not without complications though), but it is not the purpose of this action to do this.
The action is meant for things you explicitly like (or have) to run in a visible Terminal window (instead of the “background” shell).[1] So, auto-closing the Terminal window would not be in line with the purpose of the action.
If you want to run command-line programs silently in the background, I propose to use the regular “Execute a Shell Script” KM action. (Output and/or errors will still be reported, according to the action settings.)
I hope I interpreted your issue correctly.
– Tom
1: For example for graphics-like output, or colorized output that only works in the Terminal; or table output, certain interactive processes, etc. Or for things that require a password and you don’t want to pipe it through KM/AppleScript.
I actually do want the interaction of the terminal (and not to run it in the background) since there is sometimes a need to give input to the beets process running.
so are there any alternate options i can use? Perhaps just kill all terminal windows after X seconds?
You could add ‘exit 0’ to the end of the terminal commands, which should close the window.
beet import “$KMVAR_Path ; exit 0
Note that it will do so as soon as the command finishes, so if you need to see anything first, that might not be a good option, but I presume that you don’t need it since you’re referring to it as a window you don’t need.
If you only want to close the window IFF the beet command exits cleanly, use this instead:
beet import “$KMVAR_Path && exit 0
which tells exit to run only if beet also exits with an exit code = 0 aka “no errors”
Yep, this is another use-case for that action. I added it to the footnote in my reply above.
@tjluoma’s solution seems to be a good one, I would give it a try. Alternatively you could:
simply send a Quit / Force Quit to the Terminal after “X seconds”, if you are sure your processes have finished then;
via AppleScript: test if a Terminal window is busy; if not, close it. This might give false positives in certain cases.
Here an example how to close non-busy windows via AppleScript:
tell application "Terminal"
set windowCount to (count of the windows)
if windowCount is greater than 0 then
set allWindows to windows
repeat with w in allWindows
if w is not busy then close w
end repeat
end if
end tell
@tjluoma, the commands you pasted seems cool but they don't actually close there window but rather leaves a messages saying Process completed. See image: