blocks|key|1816944|text|遇到同样的情况并发现问题：https://github.com/microsoft/vscode/issues/113869#issuecomment-780072904|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1816945|我将nvm+load+code解压缩到condition+function+ref中，解决了这个问题：|style|CODE|1816946|function+load-nvm+{
++export+NVM_DIR="$HOME/.nvm"
++[+-s+"$NVM_DIR/nvm.sh"+]+&&+\.+"$NVM_DIR/nvm.sh"++#+This+loads+nvm
++[+-s+"$NVM_DIR/bash_completion"+]+&&+\.+"$NVM_DIR/bash_completion"++#+This+loads+nvm+bash_completion
++[[+-s+`brew+--prefix`/etc/autojump.sh+]]+&&+.+`brew+--prefix`/etc/autojump.sh
}

#+nvm
if+[[+"x${TERM_PROGRAM}"+=+"xvscode"+]];+then+
++echo+'in+vscode,+nvm+not+work;+use+`load-nvm`';
else+
++load-nvm
fi|code-block|syntax|javascript|1816947|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/microsoft/vscode/issues/113869#issuecomment-780072904^0|D|20|0|0|2|D|J|I|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@$A|Z|B|10|F|G]|$A|11|B|12|F|G]]|9|@]|C|$]]|$1|H|3|I|5|J|7|13|8|@]|9|@]|C|$K|L]]|$1|M|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

encountered the same situation and find the issue:
<a href="https://github.com/microsoft/vscode/issues/113869#issuecomment-780072904" rel="noreferrer">https://github.com/microsoft/vscode/issues/113869#issuecomment-780072904</a>
I extract <code>nvm load code</code> to the <code>condition function</code> ref in the issue, solved this problem:
<pre class="lang-sh prettyprint-override"><code>function load-nvm {
 export NVM_DIR=&quot;$HOME/.nvm&quot;
 [ -s &quot;$NVM_DIR/nvm.sh&quot; ] &amp;&amp; \. &quot;$NVM_DIR/nvm.sh&quot; # This loads nvm
 [ -s &quot;$NVM_DIR/bash_completion&quot; ] &amp;&amp; \. &quot;$NVM_DIR/bash_completion&quot; # This loads nvm bash_completion
 [[ -s `brew --prefix`/etc/autojump.sh ]] &amp;&amp; . `brew --prefix`/etc/autojump.sh
}

# nvm
if [[ &quot;x${TERM_PROGRAM}&quot; = &quot;xvscode&quot; ]]; then 
 echo 'in vscode, nvm not work; use `load-nvm`';
else 
 load-nvm
fi

</code></pre>

blocks|key|2242312|text|从终端打开VS代码：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2242313|code+.|code-block|syntax|javascript|2242314|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Open VS Code from a terminal:
<pre><code>code .
</code></pre>

blocks|key|1816982|text|重新启动VSCode+on+BigSur对我很有用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1816983|还可以检查用户设置，以确保其与终端使用的shell的路径匹配。|1816984|检查https://code.visualstudio.com/docs/supporting/troubleshoot-terminal-launch的其他故障排除步骤。|offset|length|1816985|entityMap|0|LINK|mutability|MUTABLE|url|https://code.visualstudio.com/docs/supporting/troubleshoot-terminal-launch^0|0|0|2|22|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

Restarting VSCode on BigSur works for me.
You can also check your user settings to make sure it matches the path of the shell that your terminal uses.
Check <a href="https://code.visualstudio.com/docs/supporting/troubleshoot-terminal-launch" rel="nofollow noreferrer">https://code.visualstudio.com/docs/supporting/troubleshoot-terminal-launch</a> for other troubleshooting steps.

blocks|key|2806114|text|OSX工作|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2806115|背景|2806116|如果VS代码是通过OSX+(或Linux)界面启动的，并且有一个外壳rc进程，它在启动期间(例如nvm)需要超过10秒才能完成。|offset|length|style|CODE|2806117|周旋|2806118|这两个已知的解决方案要么是摆脱花费超过10秒的进程，要么从命令行(即code+.)启动VS代码。|2806119|这个工作是针对我们OSX上那些不管出于什么原因而-for的人--明确地不能/不能摆脱10%2B第二个进程，以及谁的-again，不管出于什么原因--通过GUI启动VS代码。|2806120|虽然下面的内容不如VS代码只需要我们可以更改的配置，但仍然比必须记住从终端运行code+.要好得多，而且比不使用nvm+(或者切换到另一种选择)要好得多。|2806121|注意:文件扩展名确实需要在.command和.app之间更改几次--这不是一个错误！|2806122|使用以下内容创建一个新文件：
#!/bin/sh代码。|ordered-list-item|2806123|在您的“应用程序”目录中保存具有.command扩展名的文件，例如~/Applications/vs-code-cli-starter.command。|2806124|在终端中，更改新文件的权限：
chmod+%2Bx+fileName.command|2806125|在Finder中，右键单击新的app/命令并选择“获取信息”，然后在实际的VS代码应用程序中重复。|2806126|将大图标从实际VS代码的“获取信息”的“预览”部分拖到新创建的app/命令的“获取信息”的左上方的小图标。|2806127|📷|atomic|2806128|关闭两个“获取信息”面板。|2806129|在“应用程序”目录中，将文件扩展名从.command更新为.app，例如vs-code-cli-starter.app。|2806130|将新创建的应用程序图标拖到您的码头上。|2806131|在“应用程序”目录中，将文件扩展名从.app交换回.command，例如vs-code-cli-starter.command。|2806132|尽情享受|2806133|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/5584c2ad02ee7483bf515d632e42444e.png|imageAlt^0|0|0|1C|3|0|0|Y|6|0|0|13|6|0|D|8|M|4|0|0|G|8|X|16|0|0|0|0|0|1|0|0|0|I|8|T|4|10|N|0|0|I|4|P|8|10|R|0|0^^$0|@$1|2|3|4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1R|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1S|8|@$F|1T|G|1U|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|1V|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|1W|8|@$F|1X|G|1Y|H|I]]|9|@]|A|$]]|$1|N|3|O|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|20|8|@$F|21|G|22|H|I]]|9|@]|A|$]]|$1|R|3|S|5|6|7|23|8|@$F|24|G|25|H|I]|$F|26|G|27|H|I]]|9|@]|A|$]]|$1|T|3|U|5|V|7|28|8|@]|9|@]|A|$]]|$1|W|3|X|5|V|7|29|8|@$F|2A|G|2B|H|I]|$F|2C|G|2D|H|I]]|9|@]|A|$]]|$1|Y|3|Z|5|V|7|2E|8|@]|9|@]|A|$]]|$1|10|3|11|5|V|7|2F|8|@]|9|@]|A|$]]|$1|12|3|13|5|V|7|2G|8|@]|9|@]|A|$]]|$1|14|3|15|5|16|7|2H|8|@]|9|@$F|2I|G|2J|1|2K]]|A|$]]|$1|17|3|18|5|V|7|2L|8|@]|9|@]|A|$]]|$1|19|3|1A|5|V|7|2M|8|@$F|2N|G|2O|H|I]|$F|2P|G|2Q|H|I]|$F|2R|G|2S|H|I]]|9|@]|A|$]]|$1|1B|3|1C|5|V|7|2T|8|@]|9|@]|A|$]]|$1|1D|3|1E|5|V|7|2U|8|@$F|2V|G|2W|H|I]|$F|2X|G|2Y|H|I]|$F|2Z|G|30|H|I]]|9|@]|A|$]]|$1|1F|3|1G|5|V|7|31|8|@]|9|@]|A|$]]|$1|1H|3|-4|5|6|7|32|8|@]|9|@]|A|$]]]|1I|$1J|$5|1K|1L|1M|A|$1N|1O|1P|-4]]]]

<h1>OSX Work-around</h1>
<h2>Background</h2>
If VS Code is started via an OSX (or Linux) GUI interface and there's a shell rc process that takes more than 10 seconds to complete during start-up (e.g. <code>nvm</code>) VS Code simply stops trying to start-up that shell.
<h2>Work-around</h2>
The two known solutions are to either get rid of the process that takes more than 10 seconds or start VS Code from the command line (i.e. <code>code .</code>).
This work-around is for those of us on OSX who —for whatever reason— explicitly don't/can't get rid of the 10+ second process and who —again, for whatever reason— start VS Code via the GUI.
While the following is less desirable than VS Code just having a configuration that we can change, it's still better than having to remember to run <code>code .</code> from the terminal, and it's much, much better than not using nvm (or switching to an alternative).
Note: The file extension does need to be changed between <code>.command</code> and <code>.app</code> several times — this is not a mistake! ;)
<ol>
<li>Create a new file with the following:
<pre><code>#!/bin/sh

code .
</code></pre>
</li>
<li>Save the file with a <code>.command</code> extension in your &quot;Applications&quot; directory, e.g. <code>~/Applications/vs-code-cli-starter.command</code>.
</li>
<li>In a terminal, change that new file's permissions:
<pre><code>chmod +x fileName.command
</code></pre>
</li>
<li>From Finder, right click-on your new app/command and select &quot;Get Info&quot;, then repeat with your actual VS Code application.
</li>
<li>Drag the big icon from the &quot;Preview&quot; section of the actual VS Code's &quot;Get Info&quot; to the small icon in the upper-left of your newly created app/command's &quot;Get Info&quot;.
<a href="https://i.stack.imgur.com/f8gIw.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/f8gIw.png" alt="where to drag the source icon from and where to drag it to" /></a>
</li>
<li>Close the two &quot;Get Info&quot; panels.
</li>
<li>In the &quot;Applications&quot; directory, update the file extension from <code>.command</code> to <code>.app</code>, e.g. <code>vs-code-cli-starter.app</code>.
</li>
<li>Drag the newly created app's icon to your dock.
</li>
<li>In the &quot;Applications&quot; directory, swap the file extension back from <code>.app</code> to <code>.command</code>, e.g. <code>vs-code-cli-starter.command</code>.
</li>
<li>Enjoy
</li>
</ol>

blocks|key|2242366|text|在Linux中，您可以打开"alacarte“并使用命令"code”创建一个新的快捷方式，然后单击“在终端中打开”框。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2242367|​|2242368|📷|atomic|offset|length|2242369|2242370|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/72471b03fb0a3c621d92d85e0bec80e9.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

In Linux, you can open &quot;alacarte&quot; and make a new shortcut with the command &quot;code&quot; and click the box &quot;Open in a terminal&quot;.
<img src="https://i.stack.imgur.com/4Rp3l.png" alt="enter image description here" />

blocks|key|2806029|text|转到项目位置并使用代码打开。在终端(如果您在linux中)或cmd+(如果您在windows中)。这应该能解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2806030|当从vscode应用程序直接打开时，就会发生这种情况，甚至我也面临过这种情况。|2806031|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Go to project location and open with code . in terminal (if you are in linux) or cmd (if you are in windows.) That should resolve this issue.
When directly opened from vscode app it happens, even I have faced this.

blocks|key|2242421|text|这是一个非常常见的错误，或者我们可以说是抱怨vs代码，所以这里有一个解决方案--不要直接从它的图标打开vs代码，或者直接从应用程序打开vs代码，相反，您可以通过键入以下命令->+$+code，分别打开来自linux/windows终端/cmd的vs代码。如果此命令不起作用，那么重新安装vs代码，并在安装前检查所有的框，还可以通过单击鼠标的右侧，直接从文件夹打开vs代码，然后单击“与其他应用程序一起打开此文件夹”并选择vs代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2242422|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

it's a very common error or we can say complain by vs code
so here is the solution - do not open vs code directly from its icon or directly from application instead you can do is just open vs code from terminal/cmd obviously for linux/windows respectively by typing this command -&gt; $ code .
if this command is not working then reinstall the vs code and check all the boxes before installing it will also allows you to open vs code from folder directly by clicking right side of mouse and just click open this folder with other application and select vs code.

When I launch VSCode from the dock, it always complains that
<blockquote>
Resolving your shell environment is taking very long. Please 
review your shell configuration.
</blockquote>
and then a bit later
<blockquote>
Unable to resolve your shell environment in a reasonable time. 
Please review your shell configuration.
</blockquote>
According to this page, <a href="https://code.visualstudio.com/docs/supporting/faq#_resolving-shell-environment-is-slow-error-warning" rel="noreferrer">Resolving Shell Environment is Slow</a>, the first message is displayed if .bashrc takes more than three seconds and the second is displayed if it takes longer than ten seconds.
I opened a terminal in VSCode and sourced my .bashrc file
<pre><code>dpatterson@dpconsulting$ time source ~/.bashrc
real 0m1.448s
user 0m0.524s
sys 0m0.671s

dpatterson@dpconsulting$ 
</code></pre>
As you can see, it takes less than 1.5 seconds.
Environment:
<ul>
<li>MacOS Mojave 10.14.6</li>
<li>VSCode 1.53.0</li>
</ul>
Hopefully someone knows what is causing this. 
Barring that, maybe someone can point me to the code that actually generates these errors.
TIA

VSCode complains that resolving my environment takes too long

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

当我从码头启动VSCode时，它总是抱怨解析shell环境需要很长时间。请检查您的shell配置。然后再晚一点无法在合理的时间内解析您的shell环境。请检查您的shell配置。根据此页面，，如果.bashrc花费超过3秒，则显示第一条消息；如果超过10秒，则显示第二条消息。我在VSCode中打开了一个终端并获得了我的.bashrc文件dpatterson@dpconsulting$ time s

问VSCode抱怨解决我的环境需要花费太长时间。
EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VSCode抱怨解决我的环境需要花费太长时间。EN

回答 7

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问VSCode抱怨解决我的环境需要花费太长时间。
EN