Configuration Information:
Machine: x86_64
OS: darwin13.3.0
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='darwin13.3.0'
-DCONF_MACHTYPE='x86_64-apple-darwin13.3.0' -DCONF_VENDOR='apple'
-DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL
-DHAVE_CON
Configuration Information:
Machine: x86_64
OS: darwin13.3.0
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='darwin13.3.0' -DCONF_MACHTYPE='x86_64-apple-darwin13.3.0'
-DCONF_VENDOR='apple' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL
-DHAVE_
On 3/22/15 3:55 AM, Arthur20 wrote:
> Bash Version: 4.3
> Patch Level: 26
> Release Status: release
>
> Description:
> When you have already set a variable to empty, running `declare -gn
> varname` in a function twice crash bash with a Segment Fault.
Thanks for the report. This
Hey.
The bash manpage says:
>When a login shell exits, bash reads and executes commands from the
>file ~/.bash_logout, if it exists.
However, it seems that this happens only for interactive login
shells,... at least I couldn't get it executed for non-interactive login
shells with the --login opti
On 3/22/15 7:50 PM, Christoph Anton Mitterer wrote:
> Hey.
>
> The bash manpage says:
>> When a login shell exits, bash reads and executes commands from the
>> file ~/.bash_logout, if it exists.
>
> However, it seems that this happens only for interactive login
> shells,... at least I couldn't ge
Hey.
On Sun, 2015-03-22 at 22:08 -0400, Chet Ramey wrote:
> It does when you call the exit builtin. EOF to an interactive shell
> executes the exit builtin, but you have to explicitly call it when in
> a non-interactive shell.
Ah... tricky :D
Okay could you then please add this? Guess many other
