Change:
VSCODE_ZDOTDIR=$ZDOTDIR ZDOTDIR=$USER_ZDOTDIR <del> . $USER_ZDOTDIR/.zshenv </del> <ins> # prevent recursion if [[ $USER_ZDOTDIR -ne $VSCODE_ZDOTDIR ]]; then . $USER_ZDOTDIR/.zshenv fi </ins> USER_ZDOTDIR=$ZDOTDIR ZDOTDIR=$VSCODE_ZDOTDIR

Discussion:
Type: <bBug</bSince updating to 1.72.2, I have been constantly getting the following error in the integrated terminal: This path points to a file with the following contents #

if [[ -f $ ]]; then VSCODEZDOTDIR=$ZDOTDIR ZDOTDIR=$USERZDOTDIR . $ USERZDOTDIR=$ZDOTDIR ZDOTDIR=$VSCODEZDOTDIR fi vsliv368cf: vsreu685: python383: vspor879: vspor708: vspor363: vswsl492: vslsvsres303: pythonvspyl392: vserr242cf: pythontb: vsjup518: pythonptprofiler: vshan820: vstes263: pythondataviewer: vscod805cf: binariesv615: bridge0708: bridge0723: cmakevspar411: vsaa593cf: pythonvs932: cppdebug: vscaat: vsclangdc: c4g48928: dsvsc012cf: azure-devsurveyone: : vsccc: pyindex848: nodejswelcome1: 40g7c324: </details<!-- generated by issue reporter --
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.72.2. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
Worth nothing that I've just updated to following the message above, and still get the same error. Also worth noting, this issue does not happen if I: Open a new, empty VSCode window Load a folder via File Open Folder However does happen when I: Open a folder from VSCode integrated terminal, e.g. (with or without the -r flag)
Can you reproduce this in insiders? Believe this has been fixed
Same problem in insiders. Same error pointing to the same file (albeit in the directory rather than ).
This would happen if your is set to the . What is the output of ?
In my env, is set to , and doesnt exist.

<details<summaryFull env</summaryNote, this is the full output from a VSCode integrated terminal while this issue is present: </details
I see the issue - we should not be setting the zdotdir if the user_zdotdir is our temp directory
Is there any quick workaround for this?
you should be able to try the fix in insider's tomorrow
OMG this issue is so annoying! Even disabling the shell integration does not seem to help.
I actually found it working when i just restarted vscode using my launcher. When starting vscode from a terminal the issue still occurs
<!-- 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!
This does not appear to have been resolved in insiders. While I no longer see the error message mentioned in the description, my integrated terminal is still broken, in that I cannot use any of the zsh functionality. As an example, when I load the IDE via launcher and open a folder via the File Open Folder, my integrated zsh terminal works as expected, displaying something like: However when opening the editor via the terminal, my integrated zsh terminal displays something like: And in the latter case, none of the zsh functionality works. Version info After re-reading my original bug description, I realise I never mentioned that the zsh functionality wasnt working, so that's my bad. Perhaps these two issues are unrelated (recursion limit exceeded and zsh terminal becoming a "basic terminal"), but they appeared at the same time.
thanks for the info - that sounds like a separate issue. am I correct in my understanding that you see the issue when you open via the cli IE but not otherwise?
Correct, but for both and . So to confirm, opening VSCode (insiders and normal) via CLI causes this issue. However opening VSCode (insiders and normal) via app launcher is OK.
While I no longer see the error message mentioned in the description, Considering this verified as the fix was meant to prevent the recursion from happening, which worked based on the above. Will deal with the other issue separately