Sorry I accidentally sent the message immediately. I use this script:
catcher() {
echo caught.
}
set -o monitor
trap catcher SIGCHLD
for (( ;; )); do
echo sleeping.
sleep 2s &
echo reading.
read -t 5
echo --
echo waiting.
wait
don
Good day,
It seems like starting 4.3 (beta2) bash already delays handling traps until
read exits. Is this intended? It would be a problem if read has a long
timeout or doesn't have a timeout at all:
On 11 Oct 2013, at 00:22, Eric Blake wrote:
>
> Why impose an arbitrary recursion limit at all? [..]
> One way to do this is to link to the GNU libsigsegv library [..]
> (although gracefully recovering from overflow is a MUCH harder task [..]).
I personally do not mind linking with libsigsegv,
On 11 Oct 2013, at 05:55, Dan Douglas wrote:
> Objection! That would break my important aliases.
>
> $ alias exit='eval "$BASH_COMMAND"'
> $ alias shutdown='eval $BASH_COMMAND\&{,}'
I have to start using those.
I am sorry here I thought that the idea was to not allow infinite calls, I can
se
On Thursday, October 10, 2013 11:40:31 PM Piotr Grzybowski wrote:
> 2. a better place for this limit is acctually eval (probably leaving
> alias recursion limit, before Oliver starts playing with it, is also a
> good idea?):
>
Objection! That would break my important aliases.
$ alias exit='eval
On Monday, October 07, 2013 10:21:06 AM Chet Ramey wrote:
> The subshell command is clearly part of the || compound command. The
> subshell `knows' that it is part of || and set -e has no effect. This
> example has been discussed before, on this list and the austin-group
> Posix list, and the bas
On 10/10/2013 03:40 PM, Piotr Grzybowski wrote:
> a small correction, if I may; while that was all very sweet, there
> are two issues here:
>
> 1. recursion_count has to be reset somewhere, or else it is a global
> alias limit :)
> 2. a better place for this limit is acctually eval (probably leav
a small correction, if I may; while that was all very sweet, there
are two issues here:
1. recursion_count has to be reset somewhere, or else it is a global
alias limit :)
2. a better place for this limit is acctually eval (probably leaving
alias recursion limit, before Oliver starts playing with
helo all!
I agree, it is abit off a bug. That should fix it (coding and writting from
my mobile, so sorry for bad style ;-)) :
cheers,
pg
---
builtins/alias.def | 7 +++
1 file changed, 7 insertions(+)
diff --git a/builtins/alias.def b/builtins/alias.def
index d760ceb..7a7b510 100644
--- a/b
[Thu, Oct 10, 2013 at 11:38:47AM +0200] Andreas Schwab
> "Oliver J. Morais" writes:
> > Playing around with aliases, I stumbled over the following:
> > $ alias alias="eval alias"
> > $ alias foo=bar
> You have created an infinite recursion, same as f() { f; }; f.
Sure, but I think bash should not
"Oliver J. Morais" writes:
> Playing around with aliases, I stumbled over the following:
> $ alias alias="eval alias"
> $ alias foo=bar
You have created an infinite recursion, same as f() { f; }; f.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 197
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKA
12 matches
Mail list logo
