sixels, OSC

[MamiyaOtaru]

I've got this working well in a tabbed interface with a little extra plumbing for the terminal to inform the tab if it closes and vice versa.

No Sixels though! This is with Microsoft.Terminal.WPF compiled from head (from MS' terminal repo) and conpty.dll from the same. Is this a limitation of their wpf control, or something in EasyWindowsTerminalControl (and is it intractible or is there an option I am missing)?

Also, would be nice to react to OSC sequences, like setting window title, or displaying progress, or changing tab color to match new BG color set with OSC 11. Is there any way to read the output short of easyTerminalControl.LogConPTYOutput = true; and then easyTerminalControl.ConPTYTerm.GetConsoleText(); to get literally everything? Edit ReadOutputLoop in TermPTY to fire an event? look for codes when that event is picked up, or maybe only fire them from ReadOutputLoop if they are detected? Think I can see how I would go about this, just wondering if you've done anything with reacting to the text that comes through!

edit if I could subscribe to TerminalOutput events.. still poking
edit2 easyTerminalControl.ConPTYTerm.TerminalOutput += HandleText; <- OK, that's getting everything a bit at a time instead of all at once. Input as well as output. can probably get something going from there. determining whether input out output though.. all input is eventually output too head spins a bit

[MamiyaOtaru]

heck being able to click on URLs displayed with OSC 8 would be nice too :D

[mitchcapper]

Good ideas here. I think you are right as well other than adding an inline filter to catch certain sequences manually I don't think there are any events one can bind to do so for all these things. I would recommend filing an upstream feature request with these items for the base term items. If they are added I am happy to expose them (not that we really prevent direct access).