The diagnostic:

Code:

/usr/bin/tui-print: line 1: $'\342\210\222': command not found

doesn't mean that bash was trying to execute something specified using $'...', it just means that it was asked to execute a command whose name was specified as those three octal valued bytes (which do not form valid characters in the current locale), and there was no command found in $PATH matching that name. Try:

Code:

grep $'\342' ...

instead of:

Code:

grep "\$\'" ...

and if that doesn't work either, try looking for a lowercase letter b followed by a backspace. (If the last one works and you don't see why I made that wild guess, ask me after it works.)

Note that if you have something like:

Code:

$var

in your code somewhere such that it is being treated as a command name, it might be even harder to find. (Like maybe the double backslashes in the printf statement in msg_error() are causing the output from the getconf command substitutions to be executed???)

As always, bash -xv script [arg...] is your friend when trying to find out where something is going wrong.

For the record, you still have:

Code:

		trap − HUP INT QUIT ABRT KILL ALRM TERM EXIT

in your script. And in the two lines in your code:

Code:

for tc in /usr/var/tmp /var/tmp /tmp $HOME/.cache;do [ -w "$tc" ] && break;done
for tl in /usr/var/log /var/log $HOME/.config/tui/logs;do [ -w "$tc" ] && break;done

I would have guessed that the tc marked in red above should be tl.