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

2017-01-10 Thread Kang-Che Sung
On Wed, Jan 11, 2017 at 3:17 AM, Kang-Che Sung wrote: > (Note: this is a large patch. Patch included as mail attachment) > > 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 t

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

2017-01-10 Thread Kang-Che Sung
(Note: this is a large patch. Patch included as mail attachment) 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, and makes it

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

2017-01-10 Thread Kang-Che Sung
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) Signed-off-by: Kang-Che Sung --- shell/hush.c | 3 +++ 1 file changed, 3 i

Re: [PATCH] ash: fix error code regression

2017-01-10 Thread Denys Vlasenko
1.26.2 is out. On Sun, Jan 8, 2017 at 6:00 PM, Denys Vlasenko wrote: > There is a bug in ash which requires a new bugfix release (1.26.2) soon > anyway. > > On Fri, Jan 6, 2017 at 12:52 PM, Martijn Dekker wrote: >> Op 02-01-17 om 13:50 schreef Ron Yorston: >>> The commit 'ash,hush: set exit cod

Re: Please revert "ash: make dot command search current directory first, as bash does."

2017-01-10 Thread Denys Vlasenko
done. On Tue, Jan 10, 2017 at 2:43 PM, Jody Bruchon wrote: > On 2017-01-10 3:42 AM, Kang-Che Sung wrote: >> >> Please revert commit 8ad78e1ec7b2e873953f9f476fb63b5893526c39 >> "ash: make dot command search current directory first, as bash does." >> >> This dot command behavior neither follows bas

Re: Please revert "ash: make dot command search current directory first, as bash does."

2017-01-10 Thread Jody Bruchon
On 2017-01-10 3:42 AM, Kang-Che Sung wrote: Please revert commit 8ad78e1ec7b2e873953f9f476fb63b5893526c39 "ash: make dot command search current directory first, as bash does." This dot command behavior neither follows bash's behavior nor POSIX's. It is also a security risk to have the dot comman

Please revert "ash: make dot command search current directory first, as bash does."

2017-01-10 Thread Kang-Che Sung
Please revert commit 8ad78e1ec7b2e873953f9f476fb63b5893526c39 "ash: make dot command search current directory first, as bash does." This dot command behavior neither follows bash's behavior nor POSIX's. Bash behavior is: Dot command search on PATH first, *then* search the current directory. And b