-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
Allow ligatures in WebGL #5888
Allow ligatures in WebGL #5888
Conversation
The |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the ping - glad it works!
Thanks for the approval @GitSquared ! What's the process to get this merged? |
There are rendering issues with ligatures and webGL renderer |
@jacob-israel-turner Sorry, there might be some confusion here: I only approved this as someone who previously worked on that feature, I am not a core Hyper contributor and I can't merge PRs into the main branch. @LabhanshAgrawal Great job on upstream issues helping Daniel, it seems the issue has been fixed in xtermjs/xterm.js#3286 and released in https://github.com/xtermjs/xterm.js/releases/tag/4.12.0, is there anything else preventing Hyper from enabling ligatures+webgl as well? Otherwise I think this PR could be merged - the xterm.js dependency in Hyper is up to date, too. I've just enabled it on a terminal emulator with the same stack (GitSquared/edex-ui@1b4d3d5) and it works perfectly. |
@GitSquared That issue is with the 4.12 release also, it's reproducible in the xterm.js demo too. |
Thanks for your response @LabhanshAgrawal!
From the issues I've seen, I would say this statement is debatable. It seems that there are occasional wrong color for some of the ligatures. From my perspective, I have three options:
I would prefer to use option 3 while the XTerm.js team figures out the cause of the bugs. #2 is simply not an option, as the performance cost of turning off WebGL is not reasonable. Would it not be appropriate to allow users enable ligatures with WebGL, but include a disclaimer that there are known issues when mixing the two? |
Well, it's not just wrong colors, but that aside. You can actually use the hyper-font-ligatures plugin with webgl, it doesn't force you to use canvas renderer. It just loads the xterm ligatures plugin. |
If you feel strongly that users shouldn't be able to turn on ligatures with WebGL for now, then I'll go submit a PR to the |
Yeah, I think updating it on the ligatures plugin for now would be better. Or you can just put it in a local plugin. |
See discussions here for context: vercel/hyper#3607 (comment) xtermjs/xterm.js#3286 xtermjs/xterm.js#2847 vercel/hyper#5888
Opened a PR over at |
Adds ligature support for WebGL renderer.
Fixes #3607