_result="$_result '${_p//'/'\"'\"'}'"
Busybox ash has a CONFIG_ASH_BASH_COMPAT config to get this ${var//...}
replacement behaviour. And, in bash, the ' in the pattern section is treated
as a quote start. To give the ' a literal meaning, use \'
eg ${_p//\'/..repl..}
In current busybo
From: Harvey
> Sent: 14 February 2024 18:18
> Sorry, posted the wrong version of the pack_args() funtion:
> I have payed with possible solutions for so long that I forgot the
> restore the original before posting -blush-
>
> Here is the original version:
>
From: David Leonard
> Sent: 15 February 2024 08:46
> To: Harvey
> Cc: busybox@busybox.net
> Subject: Re: Failing shell code under busybox 1.36.1 that worked with 1.31.1
>
>
> > _result="$_result '${_p//'/'\"'\"'}'"
>
> Busybox ash has a CONFIG_ASH_BASH_COMPAT config to get this ${var//.
I'm using 'udhcpc' on my ARM64 platform with the following scenario: I have one
'eth0' interface that has a static ip address and the 'udhcpc' client on the
same interface. That leads to low data transmission performace on that
interface.
Most people use udhcpc when they *don't* have a static I
Am Thu, Feb 15, 2024 at 12:23:06PM + schrieb Laurent Bercot:
> > I'm using 'udhcpc' on my ARM64 platform with the following scenario: I have
> > one
> > 'eth0' interface that has a static ip address and the 'udhcpc' client on the
> > same interface. That leads to low data transmission performa
On Wed, 14 Feb 2024 14:05:15 +
Matthew Chae wrote:
> Hi Bernhard,
>
> I'm sending new patch and the result of bloatcheck.
Many thanks for the updated patch!
function old new delta
display_process_list1406
David,
I can confirm that your patch solves my problem without any further need
to change the shell code. Now V 1.36.1 acts in the same way as V 1.31.1
did. Thank you so mutch! Maybe this is candidate to merge ;)
Greetings
Harvey
Am 15.02.24 um 09:45 schrieb David Leonard:
_result
Well, I also tried adding support for bash's ${var@Q} (which I think is the
most readable way to solve quoting) but it seems I really don't understand
how ash's subevalvar() works after all :)
./busybox ash -xvc 'v="ab cd"; echo "(${v@Q})"'
+ v='ab cd'
ash: vstransform:str='Q'
ash: vstransfor
