diff options
| author | Frédéric Brière <fbriere@fbriere.net> | 2019-06-28 23:38:58 -0400 |
|---|---|---|
| committer | Frédéric Brière <fbriere@fbriere.net> | 2019-06-29 19:48:20 -0400 |
| commit | b3cca3938332011ef9b2454ba5a30f15863930ba (patch) | |
| tree | 26228c0f42ea3706cd89eb720ab09b9fed4cfc23 /twinkle_config.h.in | |
| parent | 05082ae12051821b1d969e6672d9e4e5afe1bc07 (diff) | |
| download | twinkle-b3cca3938332011ef9b2454ba5a30f15863930ba.tar twinkle-b3cca3938332011ef9b2454ba5a30f15863930ba.tar.gz twinkle-b3cca3938332011ef9b2454ba5a30f15863930ba.tar.lz twinkle-b3cca3938332011ef9b2454ba5a30f15863930ba.tar.xz twinkle-b3cca3938332011ef9b2454ba5a30f15863930ba.zip | |
Make Readline non-blocking: Use Readline's callback interface
When Twinkle is running in CLI mode and is sent a "quit" command to its
local socket, it will currently not respond immediately, but rather wait
until the next line has been read from its standard input (issue #143).
This is due to the blocking nature of readline(), which only returns
once a complete line has been read. Switching to Readline's "alternate"
callback interface is the first step in addressing this issue.
(As a bonus, this also fixes a bug where the line pointer returned by
readline() was not freed correctly.)
Diffstat (limited to 'twinkle_config.h.in')
0 files changed, 0 insertions, 0 deletions