Re: A good scripting language for busybox?

With respect to the message from Pavel Aronsky on 03/17/2017 11:20 AM: --- Apologies for maybe a wild or off-topic question. After dealing with quite a few products with busybox and its ash shell used as the primary scripting language, I'd

Re: [PATCH] add exec -a support (preliminary)

On Wed, 01 Feb 2017 15:22:39 +0100 Patrick Pief wrote > On Wed, 01 Feb 2017 07:30:46 +0100 Denys Vlasenko > wrote > > On Fri, Jan 27, 2017 at 12:56 AM, Patrick Pief wrote: > > > There were several times

[PATCH] quote arguments in xtrace output

The xtrace (set -x) output in ash is a bit of a pain, because arguments containing whitespace aren't quoted. This can make it impossible to tell which bit belongs to which argument: $ ash -x -c 'somevar="one two" printf %s\\n one "two three" four' + somevar=one two printf %s\n one two three four