From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: The `zle' command and traps
Date: Tue, 14 Mar 2000 16:56:59 +0000 [thread overview]
Message-ID: <1000314165659.ZM7956@candle.brasslantern.com> (raw)
In-Reply-To: <200003141035.LAA06725@beta.informatik.hu-berlin.de>
On Mar 14, 11:35am, Sven Wischnowsky wrote:
} Subject: Re: PATCH: Re: The `zle' command and traps
}
} Killing loops containing only builtins should work fine, because we
} set breaks=loops (and errflag, btw) in the handler -- and it /seems/
} to work fine for me.
Hrm. I got zsh into a state yesterday where running this loop:
for ((i=10000; i; --i)) echo LOOP
was not killable. I had to blow it away with 'kill -9' from another
terminal (because I'd used a much bigger number than 10000 and didn't
want to wait). I tried sending it INTs, HUPs, QUITs and TERMs with no
effect, after I was unable to ^C it.
Today when I try the same thing in a fresh shell, I'm able to interrupt
it with ^C. The unkillable shell hadn't been running for more that a
couple of hours, but long enough for me to have forgotten even vaguely
what I did to get it into that state. All I know is that it was one
where I'd been experimenting with various things ... hmmm, I bet some
function I ran, used the "trap" command without "setopt localtraps".
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-03-14 16:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-14 10:35 Sven Wischnowsky
2000-03-14 16:56 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-14 9:54 Sven Wischnowsky
2000-03-13 16:49 Sven Wischnowsky
2000-03-13 17:08 ` Bart Schaefer
2000-03-13 15:07 Sven Wischnowsky
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=1000314165659.ZM7956@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.dk \
/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).