Pass selected file path to a shell script

I don't have time to dig into the iconset format. But I created a copy of your workflow that just echoes the folders to a file. The only difference with your is that I'm using zsh instead of tcsh. But the default script it gave me is this:

for f in "$@"

do

echo "$f" > /tmp/files.txt

done

The only change I made was to redirect the output of the echo command. It worked.

LouBenjamin wrote:

My impression is that the version of bash that's installed in macOS is very old, and many of the folks who swear by that shell have installed updates over the system-installed version. Word is that Apple no longer defaults to bash, and they have deprecated it, with plans to remove it in future releases.

I’ve been using zsh for years, long before Apple started pushing people to it. zsh is every bit as powerful as bash, and virtually identical. If you had lots of very low-level bash plugins or other modifications, then you might want to keep using bash. But otherwise, most of the reason people use bash is actually the same reason Apple doesn’t - the viral GPL license. It was originally designed to stop Apple (I mean just Apple) from using GNU source code. Then, it was upgraded to ensure that it could not be used in any part of the Apple ecosystem. This way, GPL-licensed code can only be used by companies like Amazon, Facebook, and Google, who do not re-distribute it. Some people say that was always the plan.

You need a for loop in the Run Shell Script action to process one or more folders passed in as arguments. I have never used the tcsh shell, so this is the for loop with /bin/bash set as the Shell:

#!/bin/bash

for f in "$@"
do
    iconutil -c icns "${f}"
done
exit 0

Though I would be inclined to use zsh for its other strengths, Apple has not removed Bash from the operating system, or Run Shell Script actions, and the same for loop works in either shell as I shared with you earlier.