Skip to content

Conversation

@khoek
Copy link

@khoek khoek commented Feb 7, 2026

I noticed that using indicatif (and friends) to embed a hyperlink in a console progress bar caused the wheels to fall off my app (with many newlines being spammed to the console and the auto-updating line-rewriting broken). I tracked the problem down to the OSC sequences incorrectly being interpreted as printable, and the following patch fixes the problem for me.

khoek added 3 commits February 7, 2026 13:48
Treat OSC (e.g. OSC 8 hyperlinks) as non-printing when iterating/stripping ANSI codes.
Treat DCS as non-printing, including the DCS wrapper used by tmux passthrough.

Adds a regression test for tmux-wrapped OSC 8 hyperlinks.
Ensure the complex_data test fixture is present in packaged sources.
@djc
Copy link
Member

djc commented Feb 7, 2026

Appreciate the clean commit history, but it looks like there's a fair bit of code duplication. Could that be deduplicated? (If not, why not?)

@khoek
Copy link
Author

khoek commented Feb 8, 2026

Appreciate the clean commit history, but it looks like there's a fair bit of code duplication. Could that be deduplicated? (If not, why not?)

@djc Just my editorial choice to keep things simple. Did you have something more like the following (see latest commit) in mind? It's more complex but clarifies intent. (Happy to squash if you like it, honestly I kind of do.)

Either way, I think the new commit at least clearly shows why there is some subtlety due to the differences in OSC and DCS semantics/idiosyncrasies---two examples:

  • \x07 (BEL) is allowed to close an OSC sequence without needing ESC \
  • ESC \ ends both OSC and DSC, and for recovery we allow ESC EOF to terminated, but in DSC there are also escaped ESC ESCs so one needs to be sure this doesn't break ESC EOF handling.

Let me know what you like!

@khoek
Copy link
Author

khoek commented Feb 8, 2026

(Sorry about the noise I was bikeshedding a function name.)

Copy link
Member

@djc djc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I definitely like it better too -- please squash.

Is there existing stuff which could leverage the same trait?

}

fn consume_dcs_end_exclusive(it: &mut Peekable<CharIndices<'_>>, start: usize) -> usize {
fn consume_end_exclusive<S: EscSequence>(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe this could/should be a provided method on the trait?

it.next();
return end;
}
trait EscSequence {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: prefer top-down ordering. That means EscSequence comes after impls for it but before EscAction.

Also, within the trait I'd prefer on_escape(), on_char(), START (renamed from START_CHAR which just duplicates its type).

Maybe EscAction could be reformulated as a ControlFlow<(), bool>?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants