Change:
builtin return fi <ins> # Return for complex debug traps to avoid # issues like https://github.com/microsoft/vscode/issues/157851 if [[ "$(trap -p DEBUG)" =~ .*[[.* ]]; then builtin return; fi </ins> # Send the IsWindows property if the environment looks like Windows if [[ "$(uname -s)" =~ ^CYGWIN*|MINGW*|MSYS* ]]; then builtin printf "x1b]633;P;IsWindows=Truex07"

Discussion:
Type: <bBug</bAfter upgrading to 1.70.1 the integrated terminal (with shell integration enabled) is generating the following error whenever a terminal is launched and also after every command. This appears to be related to as the 1.70.1 version was the first to include the fix for that issue. The error is the same as what is set to. This seems like the command trying to be run is a string and is not being parsed like there are arguments.

VS Code version: Code 1.70.1 (, 2022-08-10T06:09:15.055Z) OS version: Linux x64 5.18.15-200.fc36.x8664 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (38)</summaryExtensionVersion ------ asciidoctor-vscode2.9.8 scratchpads0.0.7 solargraph0.23.0 vscode-markdownlint0.47.0 ansible-vault0.1.3 docs-markdown0.2.113 githistory0.6.19 gitlens12.1.2 json-tools1.0.2 opensslutils1.1.1 shell-format7.2.2 gc-excelviewer4.2.55 todo-tree0.0.215 rest-client0.25.0 vscode-jmespath0.0.6 bash-ide-vscode1.14.0 git-graph1.30.0 vscode-docker1.22.1 python2022.12.0 vscode-pylance2022.8.20 remote-containers0.241.3 remote-ssh0.84.0 remote-ssh-edit0.80.0 cpptools1.11.5 ruby0.28.1 ansible0.11.29 vscode-commons0.0.6 vscode-yaml1.9.1 bash-debug0.3.9 rufo-vscode0.0.3 code-spell-checker2.5.4 shellcheck0.19.6 pdf1.2.0 vscode-icons11.15.0 vim1.23.2 jinja0.0.8 vscode-ruby0.28.0 markdown-all-in-one3.4.3 (2 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Bump. I'm also getting this.
the fix for may not have worked for all cases?
Okay so we'll disable if there's an error
I've been looking into this a bit more and the pieces that were are good, but they just don't go quite far enough. The replacements that were leave the character in place at the beginning and end.

Adjusting the line that strips the to include the space before it and then adding lines to remove the allow the function to work as expected in my testing. Stripping the character could be done in the two commands, but I think adding two additional lines to strip is safer as it seems to me that it would be possible to have a trap without surrounding , but that may not be the case.
A little bit more playing around and and even for single commands adds the characters. For example setting the DEBUG trap to: then will return This means that this code block: could be simplified to
Based on the above comments, I don't think is the correct fix.
thanks for looking into this and your comment above makes sense
What are some verification steps for this issue?
<!-- 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!
since it's Friday of endgame, can we get some verification steps?
this isn't working for me
actually, this is working for me. add where is a command that is known in your env to your . You'll know it's one that can work because you should be able to run in by itself in the terminal without errors. Verify that shell integration still works and your command runs
I think this is the expected outcome: <img width="750" alt="image" src="https://user-"