Per Bothner

@Tyriar The "view zone" approach might work. However, I don't know anything about Monaco view zones, nor have I looked into the decorator API and implementation. I'm unclear if it...

@Jerch _ Idk if inline placing of HTML snippets is a good idea._ If by "inline" you mean in the CSS `display: inline` sense, I'm inclined to agree: It's quite...

Another demo/screenshot - the `man` command outputting rich text instead of mono-space text:  The `xt-man` command is just this script: ``` echo -en '\e]72;' man -Hcat...

@jerch _My argument is about breaking the UI so badly, that ppl will get confused, how to properly interact with it._ The use-case I'm focusing on (for now) is a...

We all agree that the VT100-terminal model have been very flexible and useful but we would like to support images, math, rich text, and complex scripts (which do not work...

If we want to add rich output (and maybe notebook functionality) to the terminal, then I believe limiting ourselves to fixed-size cells is not acceptable: * If the space for...

Of course a reasonable response is "this sounds interesting, but it is too researchy and quite beyond the scope of the xterm.js project". I agree - but I believe xterm.js...

*Zones*: If I'm understanding "zones" correctly, it's basically a 100%-width HTMLElement attached to a marker. (However, if that is all it is, it doesn't explain the amount of WebGL code,...

The BufferLine re-write: Some of the complexity is because of desire to be able to switch at run-time between the old and the new implementation (defaulting to the old) until...

The de-facto standard is xterm. It is more important to match xterm than essentially-non-existent hardware. The project is called xterm.js, not vt100.js. The demo sets the `TERM` environment variable to...