UNIX for Advanced & Expert Users

POSIX compliance is a little high to shoot for when storing binary data inside shell variables, you're not going to get it. This is a BASH script and liable to stay that way. But it can be made a better BASH script.

The question isn't really about compliance, it's about avoiding unintended problems. printf "$randomstring" will mess up whenever $randomstring contains an unintentional % character as those have special meaning to printf. pritnf "%s" "$string" avoids this, but at the cost of not expanding "\x" sequences etc inside $string.

Hi guys...

Sorry about the long delay, I am a carer now for my mother so get very little time to do anything WRT programming.

I don't think AudioScope.sh is capable of being purely 'shell', (sh), able because of the 'read' statement.

I need the '-t[secs]' argument and reading the POSIX information on here the 'shell' will only allow the '-r' argument.

It also looks like 'bash' is not recognised either or I may be missing something.

So I will be cleaning up the code to suit current methods and 'bash' only, much of which I have already done.

Thanks for the input...

Another AudioScope.sh upload soon.

Hi.

On an old Mac:

Code:

OS, ker|rel, machine: Apple/BSD, Darwin 9.8.0, Power Macintosh
Distribution        : Mac OS X 10.5.8 (leopard, workstation)
bash GNU bash 3.2.17

I see in man bash:

Code:

read [-ers] [-u fd] [-t timeout] [-a aname] [-p prompt] [-n nchars] [-d delim] [name ...]

However, you might find useful:

Code:

qprompt, timer, specific characters, prompt-string, etc.; in c
           http://www.ibiblio.org/pub/historic-linux/ftp-archives/sunsite.unc.edu/Nov-06-1994/utils/shell/qprompt-2.3.tar.gz
           ( Verified 2016.06.20, compiles with warning, worked in 64-bit )

Best wishes ... cheers, drl

Hi drl...

With the pointer to ShellCheck giving more than required by this thread and does what I need then this thread is solved.

Thanks.