Feature request: timeout callback about replxx HOT 6 CLOSED

Hello.

I am willing to accept pull request introducing a change that would provide
equivalent functionality.

I imagine adding rx->set_input_timeout( count_ms ) API call for each
rx->input(prompt) call. In case of timeout rx->input(prompt) would return nullptr and errno would be set to EINTR just like when user press CTRL+C.

I am against handling this functionality though timers or signals, or threads.

What would have to implemented is timeout aware low level (working on Linux and Windows) character reading routines.

You can look at io.cxx for place where one would start implementing such feature.

from replxx.

Requested behavior can now be achieved through replxx->emulate_key_press() API call.

from replxx.

I have experimented with using the emulate_key_press method to achieve this functionality but am failing to see how I could manage it.
Ideally I would send some key sequence that would get caught in the rx.input(prompt) loop which would then be able to handle this sequence before resuming at the point where the users actual input was at the time.

If you could describe how you imagine emulate_key_press used to get the desired behavior it would be most helpful :-)

from replxx.

I think the easiest solution is to send sequence CTRL+C and CTRL+D from other thread that measures the timeout.

rx.emulate_key_press( Replxx::KEY::control('C') );
rx.emulate_key_press( Replxx::KEY::control('D') );

Or (if you want cleaner terminal) CTRL+U, CTRL+K, CTRL+D.

from replxx.

But that would terminate the entire application. I have not been clear on my original intention for the feature request; What I need is a way to have (in the same thread) a callback being called which will perform reading from a socket that can activate commands from a remote host.
If a user is already typing a command this should be preserved and the carrier resumed from the same position after the callback has terminated.

This is the behavior of rl_set_keyboard_input_timeout as is has been implemented in libreadline.

from replxx.

It seems to me that you want to multiplex(*) stdin with sockets and it seems to me that your request for timeout API is purely accidental and unrelated to the core of your need.
In my opinion GNU readline time-out API is not meant to provide multiplexing capabilities.
I am not sure that replxx will ever support explicit timeouts API or multiplexing with other input streams as both needs can be satisfied using multi-threading.

In theory, I/O multiplexing could be added to replxx but it would result in dangerous project scope creep, replxx still has ambitions to be small and simple.
I am not sure that even GNU readline with its huge API supports your actual scenario.

• central I/O->handler dispatcher supporting stdin and other fds (sockets)

from replxx.