Re: [PATCH 1/2] hush: add [[ to the builtins list

2017-01-11 Thread Denys Vlasenko
n Tue, Jan 10, 2017 at 8:15 PM, Kang-Che Sung wrote: > Otherwise the [[ EXPR ]] construct will not run. > "hush: can't execute '[[': No such file or directory" > > It seems like this thing has not been working from the beginning :( > (commit 9d617c44d2b1135d14b7dafd01a1d3992293f4d9) It's Mike fau

Re: [PATCH 2/2] Split bash compatible extensions into separate options.

2017-01-11 Thread Denys Vlasenko
On Wed, Jan 11, 2017 at 12:32 PM, Kang-Che Sung wrote: > On Wed, Jan 11, 2017 at 4:09 PM, Denys Vlasenko > wrote: >> On Tue, Jan 10, 2017 at 8:17 PM, Kang-Che Sung wrote: >>> All of the bash compatibility options will now depend on >>> CONFIG_*_BASH_COMPAT, and CONFIG_*_BASH_COMPAT become an opt

Re: [PATCH 2/2] Split bash compatible extensions into separate options.

2017-01-11 Thread Kang-Che Sung
On Wed, Jan 11, 2017 at 4:09 PM, Denys Vlasenko wrote: > On Tue, Jan 10, 2017 at 8:17 PM, Kang-Che Sung wrote: >> All of the bash compatibility options will now depend on >> CONFIG_*_BASH_COMPAT, and CONFIG_*_BASH_COMPAT become an option that >> alone doesn't add any code. >> >> Splitting these o

Re: [PATCH 2/2] Split bash compatible extensions into separate options.

2017-01-11 Thread Denys Vlasenko
On Tue, Jan 10, 2017 at 8:17 PM, Kang-Che Sung wrote: > All of the bash compatibility options will now depend on > CONFIG_*_BASH_COMPAT, and CONFIG_*_BASH_COMPAT become an option that > alone doesn't add any code. > > Splitting these options allows more flexibility in configuration Configuration