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

New terminal ligatures have limited length even when the font supports longer ligatures #235988

Open
dragoncoder047 opened this issue Dec 12, 2024 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug terminal-ligatures upstream Issue identified as 'upstream' component related (exists outside of VS Code) upstream-issue-linked This is an upstream issue that has been reported upstream
Milestone

Comments

@dragoncoder047
Copy link

(this appears to be a bug with the new "enable ligatures in terminal" thing that is marked "preview" in settings)

Does this issue occur when all extensions are disabled?: Yes

I am using Fira Code for both the terminal and the editor, which supports "infinite ligatures", one of which is joining multiple #####################'s into one continuous mark by connecting the horizontal strokes.

This works perfectly fine in the editor windows. However when I turn on the ligatures in the terminal, it only works for about ~32 characters before the ligaturized characters vanish.

With ligatures enabled:Image

With ligatures disabled:Image

(these are homebrew install command output btw)

system info

CPUs		Apple M3 (8 x 2400)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	2, 2, 2
Memory (System)	16.00GB (0.70GB free)
Process Argv	--crash-reporter-id 3690f944-688a-4ee0-964a-0b264992b30f
Screen Reader	no
VM		0%

this is probably a problem with xterm.js but on the chance that it's with vs code's implementation of ligatures I figured I'd report it here first and let the vs code maintainers decide whether it needs to be reported upstream.

sorry for not using the built-in issue reporter but it won't let me embed an image in the body text 🤷 that is a separate problem

@Tyriar
Copy link
Member

Tyriar commented Dec 12, 2024

Nice find 👍

It is indeed a problem in xterm.js, likely it's just hitting some max width for the canvas we render to.

@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug upstream Issue identified as 'upstream' component related (exists outside of VS Code) terminal-ligatures labels Dec 12, 2024
@Tyriar Tyriar added this to the January 2025 milestone Dec 12, 2024
@Tyriar
Copy link
Member

Tyriar commented Dec 12, 2024

Upstream: xtermjs/xterm.js#5246

@Tyriar Tyriar added the upstream-issue-linked This is an upstream issue that has been reported upstream label Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug terminal-ligatures upstream Issue identified as 'upstream' component related (exists outside of VS Code) upstream-issue-linked This is an upstream issue that has been reported upstream
Projects
None yet
Development

No branches or pull requests

2 participants