Re: turning on file+line for functions with shopt -s extdebug gives error

On 3/1/2019 6:15 PM, Robert Elz wrote: > Date:Fri, 1 Mar 2019 11:00:41 -0500 > From:Chet Ramey > Message-ID: <91e964e9-a7e3-4f4e-ae9f-9ff3e3627...@case.edu> > > | It's wasteful and not particularly useful to have > | the function definition text stored internall

@Q breaks set -o nounset

Hello, with "GNU bash, version 4.4.12(1)-release (x86_64-pc-linux-gnu)" I get the following behaviour: + bash -c 'set -o nounset; echo $x' bash: x: unbound variable + bash -c 'set -o nounset; echo ${x}' bash: x: unbound variable + bash -c 'set -o nounset; echo ${x@Q}' + bash -c 'set -o nounset;

Bug: Bash forgets sourcefile and linenumber of read-in functions

In bash 4.4.12, if I have some 'library' like functions that I read in at login time, and then later call them -- under trace or under bashdb, no source is shown, as bashdb (and for trace, bash) doesn't seem to be able to retrieve the original source file name and line number where the function was