Re: Setting nullglob causes variables containing backslashes to be expanded to an empty string

2019-08-06 Thread Stephane Chazelas
[re-post via gmane as the usenet interface seems not to work again. My posts can be seen at https://groups.google.com/forum/#!topic/gnu.bash.bug/0JgBRq_778o but were apparently not forwarded to the mailing list] 2019-08-06 16:00:21 -0400, Greg Wooledge: > On Tue, Aug 06, 2019 at 06:18:27PM +,

Re: Setting nullglob causes variables containing backslashes to be expanded to an empty string

2019-08-06 Thread Robert Elz
Date:Tue, 6 Aug 2019 16:00:21 -0400 From:Greg Wooledge Message-ID: <20190806200021.gk1...@eeg.ccf.org> | Unquoted $a is a bad idea, which | may explain why it didn't receive enough testing to uncover whatever | this is. A sane person might do it if a=fo

Re: Setting nullglob causes variables containing backslashes to be expanded to an empty string

2019-08-06 Thread Greg Wooledge
On Tue, Aug 06, 2019 at 06:18:27PM +, Mohamed Akram wrote: > Bash version: GNU bash, version 5.0.7(1)-release (x86_64-apple-darwin18.5.0) > > Example: > > shopt -s nullglob > a='\x30' > echo $a > > Expected output: > > \x30 > > Actual output: > Also happens in bash 5.0 on Debian GNU/Linu

Setting nullglob causes variables containing backslashes to be expanded to an empty string

2019-08-06 Thread Mohamed Akram
Bash version: GNU bash, version 5.0.7(1)-release (x86_64-apple-darwin18.5.0) Example: shopt -s nullglob a='\x30' echo $a Expected output: \x30 Actual output:

Re: Async processes started in functions not reliably started

2019-08-06 Thread Steffen Nurpmeso
Hello Mr. Elz. Ah, that old story, you are very much welcome. Robert Elz wrote in <26245.1565045...@jinx.noi.kre.to>: |Date:Mon, 05 Aug 2019 14:05:43 +0200 |From:Steffen Nurpmeso |Message-ID: <20190805120543.bf9-u%stef...@sdaoden.eu> | || Would be nice to have s