Change:
resolved "https://registry.yarnpkg.com/@webpack-cli/serve/-/serve-2.0.1.tgz#34bdc31727a1889198855913db2f270ace6d7bf8" integrity sha512-0G7tNyS+yW8TdgHwZKlDWYXFA6OJQnoLCQvYKkQP0Q2X205PSQ6RNUj0M+1OB/9gRQaUZ/ccYfaxd0nhaWKfjw== <del> "@xterm/addon-canvas@0.6.0-beta.20": version "0.6.0-beta.20" resolved "https://registry.yarnpkg.com/@xterm/addon-canvas/-/addon-canvas-0.6.0-beta.20.tgz#078dddef70caf880b2cb121fdda37d301fc13156" integrity sha512-tHhsuqElE7LNiDJPbZzgVpmbcG2Dk6i2vh1EI+DzSByUWScDqLoeJbVPE5Xd2UW2garo24lxErpnIAlsytcA3A== "@xterm/addon-image@0.7.0-beta.18": version "0.7.0-beta.18" resolved "https://registry.yarnpkg.com/@xterm/addon-image/-/addon-image-0.7.0-beta.18.tgz#588ea2d0841cff48c63bde1bfcdf56e9494dc6af" integrity sha512-+HQ+IBmHPelzjRJ5zO3XkjbeQNr2Zrf5wAlbPhy4EGSD0mDCqHJSfzZ8wKrhx7t8qpfiA8eTpWu/M76WsEnlnA== "@xterm/addon-search@0.14.0-beta.20": version "0.14.0-beta.20" resolved "https://registry.yarnpkg.com/@xterm/addon-search/-/addon-search-0.14.0-beta.20.tgz#cac366b1be1eb02cf9fe9537933f26f227d030c8" integrity sha512-1LOL/OzWSrCBpndiBeeE2S1rxtKKgU1ucYFSG3P68W0J4VQz/Ksci1BgDKsgspj9jzpsGhdql3zwa5WEM7n4Pg== "@xterm/addon-serialize@0.12.0-beta.20": version "0.12.0-beta.20" resolved "https://registry.yarnpkg.com/@xterm/addon-serialize/-/addon-serialize-0.12.0-beta.20.tgz#5fe126194ff4dc466b92a0946e081e039a14ad21" integrity sha512-GdRCQDjLyVNBxCFnhfCWsMmuqv2PryUkOaNl4z5MqB5lBUkiEnRNY0u/s5f34+2zrijp3h0O/f9JDLW4gSUQgw== "@xterm/addon-unicode11@0.7.0-beta.20": version "0.7.0-beta.20" resolved "https://registry.yarnpkg.com/@xterm/addon-unicode11/-/addon-unicode11-0.7.0-beta.20.tgz#5d3c97320898dd6766f2dc127deb4f071c8698c2" integrity sha512-4/uwJ6lV/xJplT7hJc7sO4Im4XNvEXHnUEFIs03FFp8ZUfu3U6wcBk6/GoKMwJKJtGVNxotiD6ZzJ5v8IBH6nA== "@xterm/addon-webgl@0.17.0-beta.20": version "0.17.0-beta.20" resolved "https://registry.yarnpkg.com/@xterm/addon-webgl/-/addon-webgl-0.17.0-beta.20.tgz#443845ac5ac755cf762b105ed237b30426b07137" integrity sha512-iqvXNSTfKIcO9FBraNwdO/ixPrTHok8CBN/wjlnGLv0ZMc4zLAiKE8+PHyg9ZY38QJfS+4Ouo8KsuZwoOYfnNA== "@xterm/headless@5.4.0-beta.20": version "5.4.0-beta.20" resolved "https://registry.yarnpkg.com/@xterm/headless/-/headless-5.4.0-beta.20.tgz#af26d3d0e2cdd615ccfac4a8660181fee19898fd" integrity sha512-H/as1d67J43/CB8xt1Yg/eJMbq1yopwG1bDBKdsf2ro8A1PmJFXNzaDB+wSgoH42fCusSpLJvXtUvDLtqfvBTg== "@xterm/xterm@5.4.0-beta.20": version "5.4.0-beta.20" resolved "https://registry.yarnpkg.com/@xterm/xterm/-/xterm-5.4.0-beta.20.tgz#28bbbbc73eceb6ef3e1e095de195cf849d0cbfb6" integrity sha512-nkY91qBy5pe1HlW9LOoLcyG6v4teEsliEtUVshAO42NrJDaPniSn28O5m5832UjZOdjLCY58QlcBkZUquODGrQ== </del> <ins> "@xterm/addon-canvas@0.6.0-beta.30": version "0.6.0-beta.30" resolved "https://registry.yarnpkg.com/@xterm/addon-canvas/-/addon-canvas-0.6.0-beta.30.tgz#71139253d6ba037a2a6f26895c6e45363d9f496f" integrity sha512-rDnIgtxOrRxwDiTHec3k0+K9PVeGR79RM7kjuOd39JEHRiH9JqPjwLHLAuN4RkCDh3fHbK/rTMYe73uWj5FvBw== "@xterm/addon-image@0.7.0-beta.28": version "0.7.0-beta.28" resolved "https://registry.yarnpkg.com/@xterm/addon-image/-/addon-image-0.7.0-beta.28.tgz#c06fe0c581e5c32b71a56b8c31b16580a596ae50" integrity sha512-EIw+8vQNrl5i9rN+crc4DmYLcN66zdED1pEppShAFyQjwT+yLigbcF4QQa00eeq8xzG4NEnQbRb5R+4ZR1/G1Q== "@xterm/addon-search@0.14.0-beta.30": version "0.14.0-beta.30" resolved "https://registry.yarnpkg.com/@xterm/addon-search/-/addon-search-0.14.0-beta.30.tgz#313a44258121ed30205e18170a2865e0a432f725" integrity sha512-x4bjV++cWWHg+HZ+WyOw76AjOe+lvh/rQF7XF1wO40ROLDSR9jBUH1oN9uR4Yr4XxxFgXLEdpswMhRYKrSJG/A== "@xterm/addon-serialize@0.12.0-beta.30": version "0.12.0-beta.30" resolved "https://registry.yarnpkg.com/@xterm/addon-serialize/-/addon-serialize-0.12.0-beta.30.tgz#3472fa8cbf7d43603da558fe5b95bbeee7f7349f" integrity sha512-AQC3Yf0Ld5uURJkMak/pJGsuSaajt1hdKabFPz7MYtnCy5KHsY97yIGFkUPGYKqNg6nT7gOCS2P/tCGjDaKOqA== "@xterm/addon-unicode11@0.7.0-beta.30": version "0.7.0-beta.30" resolved "https://registry.yarnpkg.com/@xterm/addon-unicode11/-/addon-unicode11-0.7.0-beta.30.tgz#49e0caebed508f8d684363c48c09da5cb1d06619" integrity sha512-FzN+L2rvXAwsjGs+UyySPz8e6EvgZNQImX63XqUOIvPnpLWkFLc+ket4n8Bu0MwmZg99atqxepEGNpXVDRPY9A== "@xterm/addon-webgl@0.17.0-beta.30": version "0.17.0-beta.30" resolved "https://registry.yarnpkg.com/@xterm/addon-webgl/-/addon-webgl-0.17.0-beta.30.tgz#159fa6bfa8e68f37c54a9a3fbf505d389f6c9374" integrity sha512-n/4ncwUXc6rRyYA+KDVv5e/VnF/OCo4bFqycWf6wNFSEvD1AJavHm/CHi//p9rPC5gLzulKuTJdOj4jQ5St+Yg== "@xterm/headless@5.4.0-beta.30": version "5.4.0-beta.30" resolved "https://registry.yarnpkg.com/@xterm/headless/-/headless-5.4.0-beta.30.tgz#be819f4253083bf104aa6fb0d21d57dd9ef6adb4" integrity sha512-2gHdJ5NUsFZyFS8H8X+98I7NUw9cYR2+ey7lLsFvfhd1gv8eqiCPGamiWDN1sZ/fbZf+cx39h/c+AaWlLlGuBA== "@xterm/xterm@5.4.0-beta.30": version "5.4.0-beta.30" resolved "https://registry.yarnpkg.com/@xterm/xterm/-/xterm-5.4.0-beta.30.tgz#79d913f0ca0c2cd357e5f3f938d48a99d0ee4e5c" integrity sha512-ShLgCpnA9WH4EMcasJYuWoUCGu5iHp0aZNsu5L/dw16CJZ7S1lkPg2dcVu3m/agOUZDJkaHiSG7j6V+P9ejvQQ== </ins> "@xtuc/ieee754@^1.2.0": version "1.2.0"

Discussion:
Type: <bBug</bText selection in the terminal seems to render by changing the background color of text. While that seems reasonable on the surface, it does weird things with powerline type features and other highlighting that might be built into the shell. Notice in the second screenshot below that different parts of the powerline are no longer visible nor are the highlights on directories. ! ! Contrast this with Windows Terminal ! ! Perhaps vscode could blend the selection background and foreground colors with the existing colors instead of overwriting them. Or render selection as an overlay. VS Code version: Code - Insiders 1.86.0-insider (, 2023-12-08T11:53:10.286Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </detailsExtensions: none<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
It was actually a pretty big feature to get the behavior working that you're saying you want changed . The overlay option was how it worked before (and actually how it still worked with ) and it was trivial to add as it's simply rectangles drawn on top of the content. Unfortunately it has big accessibility issues as it does nothing to ensure contrast is sufficient, making the text quite unreadable. The powerline specific "problem" is happening due to the fact that powerline is essentially a hack where it alternates between the background color (which changes with selection) and special characters (which changes to ensure minimum contrast ratio). I have considered making it a little nicer, perhaps by just hiding the powerline symbols completely, but its not clear what the right behavior is here. ! We could quite easily make the above do this: ! But anything more clever than that may be a little too complex, I'm hesitant to try to track "powerline" state in the cells that simply change their background color. FWIW I also hit this problem, this is what mine looks like: !
I would make the case that if background colors in terminal output are supported then having the terminal ever overwrite those background colors is necessarily a problem. I wouldn't call powerline a hack any more than I would call highlighting directories using a background color a hack. Color conveys information in the same way glyphs do.

If I choose to output something in a particular way I don't want that information arbitrarily erased by the terminal. Either the background color is reserved for selection highlighting or it's not. If it's not reserved and users are allowed to choose background colors to convey information, then the terminal does not have the authority to erase that entirely. Munge based on user settings yes, erase no. As far as solutions, I can think of a few possibilities: existing background colors instead of overwriting them. This is what other terminals seem to do and seems like a happy middle ground. the selection background color and the existing background color. It may not meet the desired contrast though. the overlay approach to be used. Between my vscode theme and my terminal configuration I have enough control to maintain the level of contrast I need. as an opt-out and don't overwrite background colors. ! !
Thanks for taking the time to put forward the proposals. I'm leaning towards 2 and blending with the selection color @ 50% opacity. Contrast is less of a problem as the foreground changes dynamically due to minimumContrastRatio. Plus we can have some special logic on the powerline glyphs to also be included in the blending, they already do something similar in how they ignore the minimumContrastRatio requirements as they are seen as background by the user.
WIP: !
<img alt="image" src=""<br<img alt="image" src=""Tried to verify using the theme. Not sure if this is the expected result.
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
The behavior on insiders doesn't quite match WIP screenshot, which matches my desired behavior. In practice powerline background colors are still being overwritten. !
can you share your settings file? Still seems to work as expected for me !
I'm able to repro in latest insiders () with no VS Settings, no pwsh config (except loading oh-my-posh), and default oh-my-posh config.

Maybe related to oh-my-posh if you're using a different powerline implementation? pwsh config !
Can repro with oh-my-posh, looking into it !
<img width="954" alt="image" src=""Looks like it works