From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guile-user@gnu.org
Subject: Re: Web server catch keyboard interrupt and release port
Date: Wed, 16 Sep 2020 08:42:07 +0200 [thread overview]
Message-ID: <ff4a0968-abcb-a538-e8d5-a6aa486f088e@posteo.de> (raw)
In-Reply-To: <87bli6wy7e.fsf@elephly.net>
Hi Ricardo,
Thanks, that helped, found it in the Guile manual : )
Regards,
Zelphir
On 15.09.20 23:02, Ricardo Wurmus wrote:
> Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> writes:
>
>> How can I catch the keyboard interrupt? Is there something in the Guile
>> manual? I could not find it.
> “sigaction” might be of interest.
>
--
repositories: https://notabug.org/ZelphirKaltstahl
prev parent reply other threads:[~2020-09-16 6:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 19:49 Web server catch keyboard interrupt and release port Zelphir Kaltstahl
2020-09-15 21:02 ` Ricardo Wurmus
2020-09-16 6:42 ` Zelphir Kaltstahl [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ff4a0968-abcb-a538-e8d5-a6aa486f088e@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guile-user@gnu.org \
--cc=rekado@elephly.net \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).