Can anyone here tell me why a2ps behaves differently if given command line arguments in a shell script versus on an actual command line? Typing this works: a2ps -o - <ascii-file >file.ps that is, a2ps delivers its output to stdout, as its docs say. Putting this in a file fails: #!/bin/bash a2ps -o - that is, a2ps sends its output to the printer when the above file is invoked like this: script <ascii-file >file.ps I've never had a command behave differently like this; it's driving me crazy! It's as though a2ps knows whether it's being invoked in a shell script or not, and cares. Is this a well-known aspect of a2ps? Is there a workaround? It's not in their website faq. I tried using --output=- as well as -o; same result. I'd really hate to have to type all the options a2ps demands when I need to use it. FWIW, I'm using v4.13, which seems to be the latest on the a2ps website. Alternatively, can someone suggest another filter for printing ascii text that allows control over tab spacing, ie. 4 spaces instead of 8? TIA, Jim