zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: zsh-workers@math.gatech.edu
Subject: Re: zsh-3.0-pre4 released
Date: Fri, 26 Jul 1996 21:30:03 -0700	[thread overview]
Message-ID: <960726213003.ZM20287@candle.brasslantern.com> (raw)
In-Reply-To: Zoltan Hidvegi <hzoli@cs.elte.hu> "zsh-3.0-pre4 released" (Jul 27,  4:06am)

On Jul 27,  4:06am, Zoltan Hidvegi wrote:
} Subject: zsh-3.0-pre4 released
}
} Traps defined by a TRAPxxx function work as
} before.  TRAPxxx functions are undefined if the trap builtin is used to
} modify the corresponding trap.

Hmm ... you seem to be saying that

	TRAPHUP() { echo Hangup }
	trap "echo Hang UP" 1
	
causes an implicit "unfunction TRAPHUP".  What, then, happens if

	trap "echo Hangup" 1
	TRAPHUP() { echo Hang UP }

??  Does the TRAPHUP definition cause an implicit "trap - 1"?  Or do both
traps fire?

-- 
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"



       reply	other threads:[~1996-07-27  4:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199607270206.EAA04563@hzoli.ppp.cs.elte.hu>
1996-07-27  4:30 ` Bart Schaefer [this message]
1996-07-27 15:55   ` Zoltan Hidvegi
1996-07-27 18:35     ` Bart Schaefer
1996-07-27 22:06       ` Zoltan Hidvegi
1996-07-27  4:57 ` Bart Schaefer
1996-07-27 17:03   ` Zefram
1996-07-27 19:26     ` Bart Schaefer
1996-07-27 20:02       ` Zefram
1996-07-27 20:38         ` Bart Schaefer
1996-07-27 22:27   ` Zoltan Hidvegi
1996-07-30  2:22 ` Clive Messer
1996-07-30 12:18   ` Clive Messer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=960726213003.ZM20287@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=hzoli@cs.elte.hu \
    --cc=schaefer@nbn.com \
    --cc=zsh-workers@math.gatech.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).