From: Clint Adams <clint@zsh.org>
To: stephen farrell <sfarrell@almaden.ibm.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: zsh 4.0.2
Date: Sun, 8 Jul 2001 22:56:33 -0400 [thread overview]
Message-ID: <20010708225633.B29399@dman.com> (raw)
In-Reply-To: <20010708191924.ECB4FE6A7F@mind-flayer.almaden.ibm.com>; from sfarrell@almaden.ibm.com on Sun, Jul 08, 2001 at 12:19:24PM -0700
> I have a debian machine and zsh 4.0.2 works great there. But I have
> another machine for which I have to compile zsh manually. On that
> machine there is some problem with zsh not recognizing signals. I
> wonder if you have a patch to fix that problem? Thanks.
By "not recognizing" do you mean that the build process isn't finding
them and thus the output of "kill -l" is incorrect, or that
zsh isn't receiving signals?
parent reply other threads:[~2001-07-09 2:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20010708191924.ECB4FE6A7F@mind-flayer.almaden.ibm.com>]
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=20010708225633.B29399@dman.com \
--to=clint@zsh.org \
--cc=sfarrell@almaden.ibm.com \
--cc=zsh-workers@sunsite.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).