Repository navigation
Proceed with defaults if no OSC response arrives within 5 seconds - #57
Merged
Merged
Conversation
caarlos0
reviewed
Jan 31, 2022
muesli
force-pushed
the
sequence-timeout
branch
from
January 31, 2022 16:58
153af7a to
0289c9b
Compare
caarlos0
approved these changes
Jan 31, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Incomplete or fake terminals (like some CIs provide) never respond to OSC queries, so we need some timeout after which we give up waiting for a response. These queries are also essentially an async operation, as the terminal might be remotely connected via the network.