Hi Ben, > This patch silences some warnings from Shellcheck, mostly about using > POSIX $(..) command substitutions instead of old backtick > substitutions.
The script starts with '#!/bin/sh'. /bin/sh on IRIX does not support $(...). But I think no GNU maintainer is using IRIX on their development machine. Therefore it's fine with me. > - conf=`sed 's/#.*$//;/^$/d' "$conffile" | tr "\015$nl" ' '` > + conf=$(sed 's/#.*$//;/^$/d' "$conffile" | tr "\\015$nl" ' ') Is the interpretation of backslashes inside $(...) different than inside `...`? Or is this an independent fix? Bruno
