Change:
resolved "https://registry.yarnpkg.com/xterm-addon-unicode11/-/xterm-addon-unicode11-0.5.0-beta.5.tgz#6992a6f56349e67b903201d52b1ad41ba3469d93" integrity sha512-MaqnU34WTHCUAo7moB4KhynGn03RckI0JJ8E/gXe96EzuCP6bVJIKSc5pc9iFeLF4BX1SuemOqIHYl2Q3u3NTA== <del> xterm-addon-webgl@0.14.0-beta.40: version "0.14.0-beta.40" resolved "https://registry.yarnpkg.com/xterm-addon-webgl/-/xterm-addon-webgl-0.14.0-beta.40.tgz#8152b293c07f921db3a7cd3c4996dfd4d90f340c" integrity sha512-6E3KGqAFkTU6A32c6gUjkwCX+DfohN6y+j1IcTjwh5Cu92TWn4tMr5KwJlaULfmtO0e9BKZlhmucmuHTWi1F9w== </del> <ins> xterm-addon-webgl@0.14.0-beta.46: version "0.14.0-beta.46" resolved "https://registry.yarnpkg.com/xterm-addon-webgl/-/xterm-addon-webgl-0.14.0-beta.46.tgz#d25cbdf18f67e45b60782c5abe4accf2ddaf0c0f" integrity sha512-kULKDY2toIjgI8GlM0AEmi8wcBJxhv+b49tBJFYpgTV338gGD5cFfFl4zunOwO7+N0de8G5a5P16MVRjHp5ARg== </ins> <del> xterm@5.1.0-beta.63: version "5.1.0-beta.63" resolved "https://registry.yarnpkg.com/xterm/-/xterm-5.1.0-beta.63.tgz#c811680494922eab873bd36ac6fd9f5404a9e944" integrity sha512-ar7SMARh6j3GUXb4tRgbqAO+kiNu4JTPx5FYXSDHr+HHt0jBgZ+lPh4AqIFwwG1pc90lRx2cvczpE5cJhG9sdw== </del> <ins> xterm@5.1.0-beta.82: version "5.1.0-beta.82" resolved "https://registry.yarnpkg.com/xterm/-/xterm-5.1.0-beta.82.tgz#e1e4c7db5547e0b9f8a381ed59c266269363c21e" integrity sha512-/s6ueCDOmgJpLS2P5uttQLvy9Pg9uE+R0G9rnXC2e7bxks0ljnc2V4w2PMd2Iidk4oR4F/4K/rFhCPlX+cVZ3A== </ins>

Discussion:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --Version: 1.72.0 (user setup) Commit: Date: 2022-10-04T23:20:39.912Z Electron: 19.0.17 Chromium: 102.0.5005.167 16.14.2 V8: 10.2.154.15-electron.0 OS: Windows_NT x64 10.0. Sandboxed: No VSCode 1.72 created a huge regression for the Powerline glyphs in my prompt compared to 1.71. See screenshots: 71  72  I've used this same prompt for a few years now. It's been a little flaky at times depending on the VSCode version, but recently it had been displaying perfectly. I didn't really track any versions before now in regards to what looked good and what didn't, but 1.71 was looking perfect. And for what it is worth, this prompt has always looked 100% perfect in Windows Terminal. Here is my prompt (sorry, it's a bit convoluted): You'll be missing some of the bash functions in that prompt, so the easiest way to repro is something simple like this: which produces this: 
does changing help?
Your whole file would be helpful, I haven't seen any powerline rendering problems recently
For : and - Display the regression shown above Slightly dimmer  Looks perfect!  Here is my , though I did have to scrub some things that were for in-house extensions from my workplace:
This regression just got even worse in 1.73.

Now is also showing the weird rendering that and show (the original screenshot).
Ok this confused me a bit initially, we don't render those via the new custom glyphs which is the real fix to this. Created upstream: Could you verify that the characters that look bad are indeed unicode e0b8-eobf? I'm not sure currently if they're meant to be double width or if different fonts do them either single or double width.
I ran this bit of javscript (copy/pasted the powerline glyph from my prompt) and got which is E0BE Ha, of course it doesn't show correct here, but in VSCode it was displaying the glyph in the editor.
Thanks for clarifying
Do we know roughly when we'll get traction on the upstream issue? My prompt looks great in all applications accept for VSCode now. I wouldn't expect this kind of regression from VSCode usually.
hopefully it'll make it into 1.75, released early Feb.
Current state (webgl, edge dev, Hack NF): !
To verify: Test characters through using all values of using a font that does not support Nerd Font glyphs. Before ! After !