Subsequent escapes included in Truncate #21
Merged
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.
When a string is truncated and includes escape sequences, the string may be left “open ended”, i.e. the later reset code will not be there, and in a terminal this would therefore affect all following text. Like any other markup, really.
This PR changes Truncate* to scan the string filling the truncation point, collecting the subsequent escape code, and appending them. They won’t be visible, but they will offer “closure” of earlier sequences.
This PR does not evaluate the escape, only identifies and includes.
Also rename
IgnoreControlSequences→ControlSequences. We’re not ignoring them, per se, rather it’s a new mode that does different things.