Change:
resolved "https://registry.yarnpkg.com/xterm-addon-webgl/-/xterm-addon-webgl-0.12.0-beta.29.tgz#7a508595c4521d14d7ed4315a121f9e3f230a0f0" integrity sha512-NcZBsD0ar3ZpQX070hDIsyEBl/StRMNu6U+9crNpiD2rQVfkM1vcWkOv31Zlj3eu6/f8z5aStyZLRMCGFwiRbA== <del> xterm-headless@4.19.0-beta.25: version "4.19.0-beta.25" resolved "https://registry.yarnpkg.com/xterm-headless/-/xterm-headless-4.19.0-beta.25.tgz#a0a1b59f386c44458f06b8ced64e3567371cc983" integrity sha512-UswSgymk3g9i6XTpFAasnqqIvWhi+AEWT+iO3kkjII6ll+dYEQgeZAv92EnCmeRHp11u5TP+IBAo8jy+aTYbtA== </del> <ins> xterm-headless@4.19.0-beta.29: version "4.19.0-beta.29" resolved "https://registry.yarnpkg.com/xterm-headless/-/xterm-headless-4.19.0-beta.29.tgz#9151a1506ddcad3402ce456bbbc6af0828952742" integrity sha512-wAPyWOp2whY9kT9NL7PMQtvR/A9UO1A4bhP0nOOhZxg9GDeCy5EvsuDn2x+dtsh4jK/L2SZxM6SPHLpNoZpbTQ== </ins> <del> xterm@4.19.0-beta.25: version "4.19.0-beta.25" resolved "https://registry.yarnpkg.com/xterm/-/xterm-4.19.0-beta.25.tgz#38f92d0fef1cfdb290ef8994449a04fa1a8c90a7" integrity sha512-pDiMWKN1Cj4+X/K9Xegp0SA0ZDEGVqiq7RPSy8oZO2wo2rze1BF20PAZb3/RSp30eY5WyOKilKnck4yNOsPzHw== </del> <ins> xterm@4.19.0-beta.29: version "4.19.0-beta.29" resolved "https://registry.yarnpkg.com/xterm/-/xterm-4.19.0-beta.29.tgz#f0727ddbfe54f3c34a58e57ecbfcbb4d03a30386" integrity sha512-ZlgrxgotcCB06W0Pk5ClHDkIDE62s1LebgehEsmaksJJtoOQJIxCVu1Kop4EnnPQzZxFaG7uYumfwe0tfd6uWA== </ins> y18n@^3.2.1: version "3.2.2"

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 <!-- 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. --- VS Code Version: 1.67 OS Version: Arch Linux x86_64 & macOS 12 I'm using powerlevel10k theme for my zsh shell. Up until now everything was fine. My MacBook has the same configuration (oh-my-zsh plugin manager, powerlevel10k theme, MesloLGS NF font) and after update the problem appeared. How it was (1.66) ! How it is now (1.67) !
I believe that I have the same issue, I'm using p10k and zsh, my font is Caskaydia nerd font (not mono, the one with double-width icons). Before the update, it rendered fine. After the update, the icons got chopped in half. Screenshot for the current vscode terminal: ! This screenshot is from gnome-terminal since I cannot rollback vscode version, but this is how the vscode terminal used to be: ! edit: add my macbook vscode terminal before: ! after: !
Have already fixed this upstream in I believe. Will be fixed in insiders shortly when we update that
Duplicate
Ah ok... thanks
I don't think so. This is not about colors but about the symbols being cut off. Also, I've set , which seems to be the fix for the other issue, and my icons are still cut off.
Actually, you can downgrade the VS Code if you install it from Chaotic AUR.
Wow, that's great, thank you. Then I'll close the issue when this fix arrives.

Same issue here on PopOS 20.04, using ZSH with PowerLevel10k and a NerdFont-patched version of Roboto Mono. !
Any way we can confirm this by testing?
I am confident this will fix it. It would be helpful if you could verify that it's fixed once this issue gets the label in a few days.
Same issue on Manjaro / zsh / p10k !
Just updated Insiders v1.68 to and the issue isn't yet fixed
Not seeing any cut off icons in insider's - please include a screenshot and the name of the font you're using if you are !
!
I used "MesloLGS NF" font with the same issue on insiders as well. P.S: : this setting seems to fix it temporarily until a fix is issued.
Yes I can reproduce the problem by changing
I'm still on the stable (non-insider) build and can confirm, that the issue goes away when setting GPU acceleration to "canvas". Somewhere, I read this before, but it was pointing to another settings option that doesn't seem to exist anymore.
This doesn't seem to happen on Windows !
Actually this appears to be fixed already, can repro in 1.67 but not in insiders
To clarify my above comment, this is fixed in the webgl renderer but not the DOM renderer (tracked in ). If you moved to I recommend switching back to or when this lands in stable as you'll get much better performance.
! ! This problem seems to be reproduced on ver. 1.67.2 Can anyone comfirm this please? Thank you so much. Temporarily moved to until fix
it's fixed in 1.68 which isn't out yet.
Thank you for your reply. I see, since this issue didn't appear in 1.67.1 so I thought it was fixed.
For me this issue is fixed now. is set to "" and symbols in the terminal are still looking fine.