Hmmm... that's odd. If you create a new file and paste the script into it? A .command file should open a Terminal.app window. That's what it does on my system. If you do "get info" you should see that it says open with Terminal.app

You can even use it to ask for keyboard input using a "read" command in bash.

[ Reply to This | # ]

As so often, it would have been best to trust one's first instincts. They were not to trust SubEthaEdit and use TextWrangler instead.

The problem was that copying the code out of Camino created text with CR as newline commands. When pasting this into SubEthaEdit, the program asks whether to keep the line endings or convert them. I naturally don't allow any apps to convert things without telling me exactly what it does. That means, I ended up with a file that had CR as newline commands but was happily showing LF at the bottom (which I naturally checked once things did not work and is my default for new files in SubEthaEdit).

Therefore, don't use SubEthaEdit because it allows you to do nonsense (mixed line endings in the same file) without any means to see which lines have which ending and without an obvious way to change the line endings (the only way to change line endings in file with mixed ones in SubEthaEdit is copy and paste all into a new file and ask it to convert the line endings).

[ Reply to This | # ]