Implement double-height/width sequences (DECSWL/DECDWL/DECDHL)

xterm supports these but xterm.js does not.

#!/bin/sh
msg="Hello world!"
clear
printf "\e[1;1H"     # move to line 1, col 1
printf "\e#3${msg}"  # top-half of the message
printf "\e[2;1H"     # move to line 2, col 1
printf "\e#4${msg}"  # bottom-half of the message
printf "\e[3;1H"     # move to line 3, col 1
printf "\e#6${msg}"  # double-width message
printf "\e[4;1H"     # move to line 3, col 1
printf "${msg}\n"    # just a normal text

[Tyriar]

Why do you care about VTE that much?

VTE is the base of many terminals and a good test of whether we should implement something. It’s not just a question of whether xterm supports it, it’s more about if most terminals support it or want to support it. There isn’t much point in implementing something that would be a pain to maintain when so few people use it due to support.

Your project has “full xterm terminal in your browser” in its title

We should change that, xterm has a ridiculous amount of stuff and no one comes close to supporting everything AFAIK. The focus of xterm.js is more to enable the implementation of modern terminals, not so much support APIs that are rarely used. There is also the fact that xterm.js runs in browsers which enforces additional constraints on size and speed. In fact we had a discussion on just this recently and the tagline we’re likely going to move to is “A terminal for the web”

If you insist on not having this in the core, just give me #1176 and I’ll write a couple of plugins for these extra features

I have hundreds of competing priorities. All good things come in time. It would be great to get some feedback/help on #1176 from someone who wants to use the API though.

[ztmr]

So are we discussing xterm.js or vte.js? Why do you care about VTE that much? In the same way, I could argument that PuTTY/pterm does support this feature too. Your project has “full xterm terminal in your browser” in its title so I would expect it to be as much compatible with xterm as possible.

(u)xterm is the only FOSS terminal emulator close enough to the real hardware VT-series terminals so that people like me have never switched to anything else because we do need and we do use these features, althought some are missing even there. If there was no need, I wouldn’t bother asking this and wasting other people’s time reading this. That is also why I was so excited to see there is a project trying to implement full xterm for web.

If you insist on not having this in the core, just give me #1176 and I’ll write a couple of plugins for these extra features. I prefer much more to help you designing/implementing these interfaces than maintaining a fork just to support something I need but you don’t want it here.