diff options
author | Frédéric Brière <fbriere@fbriere.net> | 2019-06-29 08:29:54 -0400 |
---|---|---|
committer | Frédéric Brière <fbriere@fbriere.net> | 2019-06-29 19:48:27 -0400 |
commit | cedd61a753785831f71ae5582c134c816c92700d (patch) | |
tree | 6a0c9f02d32b2bb0bab15101b8e9ea35b5700a11 /AUTHORS | |
parent | b3cca3938332011ef9b2454ba5a30f15863930ba (diff) | |
download | twinkle-cedd61a753785831f71ae5582c134c816c92700d.tar twinkle-cedd61a753785831f71ae5582c134c816c92700d.tar.gz twinkle-cedd61a753785831f71ae5582c134c816c92700d.tar.lz twinkle-cedd61a753785831f71ae5582c134c816c92700d.tar.xz twinkle-cedd61a753785831f71ae5582c134c816c92700d.zip |
Make Readline non-blocking: Relay SIGWINCH to Readline
When using Readline's callback interface, signals are (by default) only
captured within the duration of the rl_callback_read_char() call. It is
therefore expected of the application to capture SIGWINCH on its own,
and notify Readline of the fact.
(While it's possible to change this with rl_persistent_signal_handlers,
some signals, such as SIGHUP, will still only be *processed* during that
call, making it a somewhat unappealing solution. This all could be
alleviated by calling rl_check_signals() periodically, but that function
was only introduced in Readline 8.0, which is far too recent.)
Note that we are using signal(2) and not sigaction(2), depite the
various warnings that come with it, mostly because it's what is already
present in the codebase.
Diffstat (limited to 'AUTHORS')
0 files changed, 0 insertions, 0 deletions