Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: zsh-3.0-pre4 released
- X-seq: zsh-workers 1792
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: Zoltan Hidvegi <hzoli@xxxxxxxxxx>
- Subject: Re: zsh-3.0-pre4 released
- Date: Sat, 27 Jul 1996 11:35:30 -0700
- Cc: zsh-workers@xxxxxxxxxxxxxxx
- In-reply-to: Zoltan Hidvegi <hzoli@xxxxxxxxxx> "Re: zsh-3.0-pre4 released" (Jul 27, 5:55pm)
- References: <199607271555.RAA13240@xxxxxxxxxxxxxxxxx>
- Reply-to: schaefer@xxxxxxx
On Jul 27, 5:55pm, Zoltan Hidvegi wrote:
} Subject: Re: zsh-3.0-pre4 released
}
} > TRAPHUP() { echo Hangup }
} > trap "echo Hang UP" 1
} >
} > causes an implicit "unfunction TRAPHUP"
} >
} > trap "echo Hangup" 1
} > TRAPHUP() { echo Hang UP }
} >
} > causes an implicit "trap - 1"
}
} Yes or course. That's quite similar to the old behaviour.
OK, that's very good; but I think the documentation of this is a bit
misleading. E.g. from the FAQ:
! Traps defined by the trap builtin are now executed in the current shell
! environment and not as a shell function. This means that $1 is not set
! to the signal number. Of course the TRAPxxx functions continue working
! as before.
This sounds as though TRAPFOO() continues to fire ("functions continue
working") even after `trap bar foo`; sort of as if TRAPxxx() and "trap"
are now in completely separate "namespaces".
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
New male in /home/schaefer:
>N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday"
Messages sorted by:
Reverse Date,
Date,
Thread,
Author