VSCode 不会从集成终端在新选项卡中打开文件
几个月后，我在没有处理该项目的情况下打开了一个远程工作区，我发现我无法再使用集成终端在新选项卡中打开文件。经过一番谷歌搜索后，这似乎与主题 69417211 类似，但没有解决方案。这是我使用“verbose”得到的结果：
code file.txt --verbose
[70606:0302/113210.012652:ERROR:browser_main_loop.cc(1402)] Unable to open X display.
The futex facility returned an unexpected error code.
我不知道“futex”是什么，也不知道它为什么要寻找 X 显示。我尝试在本地安装“远程开发”扩展，但这没有改变任何东西。我仍然可以使用浏览器打开文件，但这并不总是一个选项，而且很少方便。
本地 VSCode 关于：
版本：1.64.2（用户设置）
提交：f80445acd5a3dadef24aa209168452a3d97cc326
日期：2022-02-09T22:02:28.252Z
电子：13.5.2
铬：91.0.4472.164
Node.js：14.16.0
V8：9.1.269.39-电子.0
操作系统：Windows_NT x64 10.0.19044
远程：
Visual Studio 代码 1.64.2
I opened up a remote workspace after a couple months without working on the project and I find that I can no longer open files in new tabs using the integrated terminal. After some Googling, this seems to be similar to the topic 69417211 but there was no resolution there. This is the result I get with 'verbose':
code file.txt --verbose
[70606:0302/113210.012652:ERROR:browser_main_loop.cc(1402)] Unable to open X display.
The futex facility returned an unexpected error code.
I don't know what 'futex' is and I don't know why it is looking for an X display. I tried installing the "remote development" extension locally but that didn't change anything. I can still open files using the browser, but that is not always an option and rarely convenient.
Local VSCode About:
Version: 1.64.2 (user setup)
Commit: f80445acd5a3dadef24aa209168452a3d97cc326
Date: 2022-02-09T22:02:28.252Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19044
Remote:
Visual Studio Code 1.64.2
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我在这里找到了解决方案：
https://github.com/microsoft/vscode- remote-release/issues/6289
基本上，需要选中“inheritEnv”框。关闭并重新打开终端后，“代码”注释将按预期工作。
I found the solution here:
https://github.com/microsoft/vscode-remote-release/issues/6289
Basically, the 'inheritEnv' box needs to be checked. After closing and reopening a terminal, 'code' note works as expected.