James Holderness

> My thinking with the separator was, that it would allow to handle arbitrary unicode content, thus also multiple chars from complicated scripting systems at once. Yeah, that seemed like...

> normal buffer - left to decide by the terminal itself (not sure, might cause frictions, then unset) I suppose it's up to the terminal to decide, but personally I'd...

> I do keep track of the previous grid coordinate, so that unwrapping would be possible with some additional logic when U+FE0E is received and previous text character changed coordinate...

I don't have the bandwidth to follow this discussion closely, but I think I'm broadly in agreement with most things you guys have been saying. One point I would suggest...

> What needs to be done in order to get WT buying in? There's an issue in the WT tracker (https://github.com/microsoft/terminal/issues/8000) where they've been discussing support for more advanced features...

That looks good to me. I was expecting it to be more complicated, but if everything else is covered by the linked Unicode documentation then that's brilliant. Answers to some...

FYI, there's a whole section on the workings of the status line in the DEC STD-070 manual, assuming you have a copy of that. It's in chapter 14 - labelled...

Ultimately I'd like to implement most of the DEC VT sequences, and I believe the status display extension is a requirement for level 3, so it's definitely on my TODO...

That's looking good. I'm not sure about the multi-line status thing though. I vaguely recall some of the DEC terminals having an additional line for keyboard status below the main...

This is probably the one DEC feature that I'm not really interested in implementing. As I understand it, `DECEDM` is part of the _Local Editing_ extension, which looks extremely complicated...