On 10/30/17 2:56 PM, PJ Eby wrote:
> Bash Version: 4.4
> Patch Level: 12
> Release Status: release
>
> Description:
> declare -F fails if function name contains '[', even if it exists.
> This makes it impossible to get the line number and file for such
> functions, as it is only available via dec
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-musl
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-musl' -DCONF_MACHTYPE='x86_64-pc-linux-musl'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/local/share/locale'
On 10/29/17 8:05 PM, Steve Jones wrote:
> While writing a function to save the directory stack as a script, I
> noticed that ${DIRSTACK[0]}, the current directory always has the tilde
> unexpanded.
>
> This is the same with bash-4.4.12 and bash-4.3.11.
>
> I was wondering if this is an oversight
On 10/29/17 10:34 PM, Clark Wang wrote:
> See following example:
>
> [STEP 100] # echo $BASH_VERSION
> 4.4.12(2)-release
> [STEP 101] # v=\'\'
> [STEP 102] # printf '%q\n' "$v"
> \'\'
> [STEP 103] # printf '%s\n' "${v@Q}"
> ''\'''\'''
> [STEP 104] #
This is an effect of using single quotes in the
On 10/29/17 10:48 PM, Clark Wang wrote:
> See following example:
>
> [STEP 100] # echo $BASH_VERSION
> 4.4.12(2)-release
> [STEP 101] # v=abc
> [STEP 102] # printf '%q\n' $v
> abc
> [STEP 103] # printf '%s\n' "${v@Q}"
> 'abc'
> [STEP 104] #
>
> Is it possible to not quote the result since there's
On 10/30/17 8:06 AM, Boruch Baum wrote:
> Is there a way to optionally turn off the verbose option for traps when
> running 'fc'? Toggling the verbose option from the command line only
> makes things more verbose for me (it echoes $PROMPT_COMMAND).
>
> For me, the desirable behavior would be for
On Mon, Oct 30, 2017 at 10:34:47AM +0800, Clark Wang wrote:
> See following example:
>
> [STEP 100] # echo $BASH_VERSION
> 4.4.12(2)-release
> [STEP 101] # v=\'\'
> [STEP 102] # printf '%q\n' "$v"
> \'\'
> [STEP 103] # printf '%s\n' "${v@Q}"
> ''\'''\'''
> [STEP 104] #
What's the bug? They are e
On Mon, Oct 30, 2017 at 12:05:51AM -0400, Eli Barzilay wrote:
> Again, `unset` has different expectations, because it seems like it
> would be a special construct
Only to you, and only because you brought in some expectations from
a different language.
> -- since it's dealing with *lvalues*.
woo
On 2017-10-28 15:40, Chet Ramey wrote:
> On 10/27/17 10:53 AM, Eduardo Bustamante wrote:
> > On Fri, Oct 27, 2017 at 1:21 AM, Boruch Baum wrote:
> >> In Debian, using Bash version 4.4, path level 12, I've set a DEBUG trap
> >> in my .bashrc and tried running the following command, with the
> >> fo
