You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the rlwrapped command changes its interrupt character (usually from CTRL-C to something else), rlwrap only follows suit after the next user input. It probably could already do this after the next client output (which will cover a lot of cases where the client does this at program start, and then outputs some kind of welcome banner)
Of course one can always use rlwrap --polling, but this will come at a cost (e.g.in battery life)
The text was updated successfully, but these errors were encountered:
Another idea would be to let even a non--pollingrlwrap poll once say 0.1 secs after spawning the client. Again, this would cover a great number of cases (though not all of them) where the client changes or disables its interrupt characters.
When the
rlwrap
ped command changes its interrupt character (usually fromCTRL-C
to something else),rlwrap
only follows suit after the next user input. It probably could already do this after the next client output (which will cover a lot of cases where the client does this at program start, and then outputs some kind of welcome banner)Of course one can always use
rlwrap --polling
, but this will come at a cost (e.g.in battery life)The text was updated successfully, but these errors were encountered: