Don't call poll when keyseq_timeout is set to 0 to avoid broken poll implementation for devices on MacOS. #802
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The poll system call is broken on MacOS and doesn't work properly for devices, such as
/dev/tty
.As a result, reading single escapes is broken when using
Behavior::PreferTerm
, which causesrustyline
to read from/dev/tty
. After reading a single escape character, the subsequent call topoll
will always returnOk(1)
, sorustyline
will try to parse an escape sequence.This PR makes a small change to at least improve the behavior when
keyseq_timeout
is set toSome(0)
. In this case, we bypass the call topoll
altogether, and instead check whether there is any buffered input to determine whether a single escape keypress has been entered or if an escape sequence has been entered, which is a pretty effective heuristic.I don't know if there's any good workaround for the broken poll implementation when
keyseq_timeout
is non-zero, but this is at least an improvement.This should resolve #607.