Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do you need anything from xterm.js? #542

Closed
Tyriar opened this issue Dec 7, 2018 · 8 comments
Closed

Do you need anything from xterm.js? #542

Tyriar opened this issue Dec 7, 2018 · 8 comments

Comments

@Tyriar
Copy link
Contributor

Tyriar commented Dec 7, 2018

Hi @Eugeny, I'm one of the maintainers on xterm.js. I noticed that hterm appears to be the default frontend and was wondering if there were particular issues on our side for this?

@MrKumaPants
Copy link

@Tyriar How about getting to work on TrueColor? :/

@Tyriar
Copy link
Contributor Author

Tyriar commented Dec 9, 2018

@MrKumaPants we're getting fairly close to done with the buffer improvements that will allow us to do true color without taking way too much memory xtermjs/xterm.js#791

@Eugeny
Copy link
Owner

Eugeny commented Dec 10, 2018

Hey Daniel, thanks for reaching out!

I've recently posted two feature requests that would definitely make it easier to switch over to xterm in the future:

xtermjs/xterm.js#1803
xtermjs/xterm.js#1824

I'm definitely looking forward to the WebGL renderer as well.

One major pain of integrating xterm is how monkeypatching-resistant it is - with a lot of stuff locked away within closures - e.g. it's absolutely impossible to patch any event handlers installed with addDisposableDomListener(), and the function itself is unreachable from xterm when it's built.

I've considered importing xterm/src/xterm.js directly, which would make all submodules importable on our side as well, but that doesn't work nicely since Terminus has stricter code policy (noUnusedLocals etc), and it results in a ton of build warnings, which TypeScript can't ignore on per-module basis.

@Eugeny
Copy link
Owner

Eugeny commented Dec 10, 2018

Also, what's the state of ConPTY integration in node-pty? The PR looks feature-complete, but I hadn't have a chance to test it yet. I wouldn't mind adding it to Terminus before it's released/stable.

@Tyriar
Copy link
Contributor Author

Tyriar commented Dec 10, 2018

I commented on those 2 issues.

One major pain of integrating xterm is how monkeypatching-resistant it is - with a lot of stuff locked away within closures - e.g. it's absolutely impossible to patch any event handlers installed with addDisposableDomListener(), and the function itself is unreachable from xterm when it's built.

Do you have some examples of what you're trying to do here?

I'm definitely looking forward to the WebGL renderer as well.

Ditto, it's not a priority to push that in currently but I'm going to keep the PR up to date in the meantime.

Also, what's the state of ConPTY integration in node-pty? The PR looks feature-complete, but I hadn't have a chance to test it yet. I wouldn't mind adding it to Terminus before it's released/stable.

It doesn't work in Electron 2 so it's been blocked on VS Code adopting Electron 3, which is likely to happen in the next release so expect me to clean up and merge that PR soon 😃

@Eugeny
Copy link
Owner

Eugeny commented Dec 10, 2018

Thanks!
As to monkey-patching, one example would be hooking the paste events.

@Eugeny
Copy link
Owner

Eugeny commented Dec 15, 2018

@MrKumaPants I've just added True Color support in #23

@Eugeny Eugeny closed this as completed in 100436f Feb 9, 2019
@Eugeny
Copy link
Owner

Eugeny commented Feb 9, 2019

xterm frontend is now the default

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

No branches or pull requests

3 participants