On Jun 11 09:35, Chet Ramey wrote:
> On 6/11/15 4:08 AM, Miroslav Koskar wrote:
>
> > In fact group command { ... } would work too, as I've showed and you've
> > confirmed. One last bit here I guess, why is it that the $BASH_SUBSHELL,
> > would not reflect that is it in fact running in subshell?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 6/11/15 4:08 AM, Miroslav Koskar wrote:
>> So the idea is that the output of `trap' can be piped. This came in in
>> Posix-2008 and bash-4.2.
>
> I've forgot to check POSIX for this, that's a good point. So to get
> list of traps corresponding to
On 6/10/15 9:27 AM, Adam Endrodi wrote:
>
> --- bash-4.2/doc/bash.1.orig 2015-06-10 15:09:04.0 +0200
> +++ bash-4.2/doc/bash.1 2015-06-10 15:19:55.0 +0200
> @@ -117,6 +117,18 @@
> This option allows the positional parameters to be set
> when invoking an interactive shell.
Hi,
as opposed to having a fancy colored prompt, I would like to be able to
set up coloring of the whole bash command input line (but not the
following command output). This could be achieved by adding a variable
like "AFTERPROMPT_COMMAND" which is executed after a prompt line is
completed (or
On 6/9/15 7:42 PM, Reuben Thomas wrote:
> At least in bash 4.3, the documentation for history -a says:
>
> Append the new history lines (history lines entered since the
> beginning of the current Bash session) to the history file.
>
> This is unfortunately misleading, since it
> There is a bug of some sort in bash 4.3.30 (and likely others) when
> compiled with --disable-job-control on Linux/x86_64.
>
> The following script will produce output after running for about 30 seconds:
> while true; do dfOutput="$(/bin/echo test)"; if echo "${dfOutput}" |
> /bin/
On 6/9/15 3:42 PM, Jean Delvare wrote:
> I think I have a minimal test case now:
>
> #!/bin/bash
>
> declare -a ARRAY
>
> ARRAY[0]=foo
> FOO=${ARRAY[0]} # <-- leaks
> echo $FOO
>
> And a candidate fix:
>
> bash 4.3: Fix memory leak in parameter_brace_expand_word
Thanks for the report. This
On Jun 09 07:39, Chet Ramey wrote:
>
> Close. What you call the `implicit' and `explicit' pipelines (subshells)
> actually both inherit the trap strings, but not the actual signal
> dispositions. Posix says this:
>
> "The trap command with no operands shall write to standard output a list
> of
