Re: bash --debugger on a script with no arguments

On Tue, May 5, 2015 at 2:54 PM, Chet Ramey wrote: > On 4/30/15 9:27 AM, Chet Ramey wrote: > > On 4/29/15 10:31 PM, Rocky Bernstein wrote: > > > >> $ ./bash --debugger -i /tmp/foo.sh > >> hi > >> > >> $ ./bash --debugger /tmp/foo.sh > >> bash debugger, bashdb, release 4.3-0.91 > >> > >> Copyrig

Re: bash --debugger on a script with no arguments

On 4/30/15 9:27 AM, Chet Ramey wrote: > On 4/29/15 10:31 PM, Rocky Bernstein wrote: > >> $ ./bash --debugger -i /tmp/foo.sh >> hi >> >> $ ./bash --debugger /tmp/foo.sh >> bash debugger, bashdb, release 4.3-0.91 >> >> Copyright 2002, 2003, 2004, 2006-2012, 2014 Rocky Bernstein >> This is free so

Re: Possible bug in 'unset' builtin

On 5/1/15 2:26 PM, Dreamcat4 wrote: > Hello. > If you unset a function, then a variable argument (argv) specified after > that function will not be unset. Thanks for the report. Yes, once you unset a function, it's as if you supplied the `-f' option. This came in as the result of a fix for the u

Re: Uxexpected complaint of "unbound variable"

On 5/4/15 9:03 PM, James Caccese wrote: > I posted the following question to stackoverflow > (http://stackoverflow.com/questions/30042157/why-cant-i-use-declare-r-inside-a-function-fo-mark-a-variable-readonly-while) > and was advised the behavior I was witnessing was a bug in bash. It's not a bug;