[解决方案] VSCode调试卡死，terminal无法输入、一片空白 （原因：由anaconda导致）
terminal
The new Windows Terminal and the original Windows console host, all in the same place!
项目地址：https://gitcode.com/gh_mirrors/term/terminal
免费下载资源
·
前言
如题，本文旨在解决一次由anaconda导致的VSCode调试卡死，以及terminal无法输入、一篇空白的问题。
场景
- VSCode
- 多个Python环境，包括conda环境
我在进入VSCode的时候，它自动在右下角给我发送了一个信息，大概是检测到conda环境，是否需要改变某个setting里面的值从而让VSCode支持conda？Yes？No？
我手贱，点了yes。
然后发现调试都调试不了了！！！给我气晕了。
解决方案
找了很久很久，没有找到这种解决方案啊。
太急了。
现在事情很多，没法一一细致研究。
试了重启什么的，没用啊。
最后受启发：
结合我遇到问题的场景。
我打开VSCode的setting（点击：File -> preferences -> settings），点击下图的Edit in settings.joson
然后在settings.json里面将"terminal.integrated.inheritEnv": false 改为"terminal.integrated.inheritEnv": true
重启一下VSCode（可以关了重开，或者Ctrl + Shift + p -> reload window。都行）
然后就可以了！！！
百病全消
小结
各种各样的问题是真的麻烦。有时候也不知道自己在这个过程中到底有收获有长进没有。
可能是徒劳无功？确实不知道。还是有点迷茫的
GitHub 加速计划 / term / terminal
8
0
下载
The new Windows Terminal and the original Windows console host, all in the same place!
最近提交(Master分支：4 个月前 )
ba87ab52
The conhost window uses the window message WM_GETDPISCALEDSIZE to scale
its client rect non-linearly. This is done to keep the rows and columns
from changing when the window changes (font sizes scale non-linearly).
If you size the window such that the text perfectly fits the width (and
cursor is on the first row of the next line), dragging the window
between monitors with different DPIs should NOT change how much of the
text fits on each line.
https://learn.microsoft.com/en-us/windows/win32/hidpi/wm-getdpiscaledsize
The current code is assuming that the size that should be scaled is the
current window size. This is sometimes the case, for example when
dragging a window between monitors, but it is not always the case. This
message can sometimes contain a size that is different from the window's
current size. For example, if the window is maximized, minimized, or
snapped (the size in these cases is the normal rect, or restore rect).
The msdn page above does (now) call this out, though it is possible that
this was added after this conhost code was added...
> The LPARAM is an in/out pointer to a SIZE struct. The _In_ value in
the LPARAM is the pending size of the window after a user-initiated move
or a call to SetWindowPos.
If the window is being resized, this size is not necessarily the same as
the window's current size at the time this message is received.
This incorrect assumption can cause the conhost window to be
unexpectedly large/small in some cases. For example:
1. Requires two monitors, set to different DPIs.
2. Size window somewhat small, and type text to fit exactly the width of
the window, putting cursor on first row of next line.
3. Win+Left (or otherwise snap/arrange the window).
4. Win+Shift+Left (migrates the window to the other monitor)
5. Win+Shift+Down (restore window, can also click maximize caption
button twice, maximizing then restoring)
Expected: The window should restore to the original logical size, with
the text perfectly fitting one line.
Actual: The window restores to another size; it is the snapped size on
the original monitor (the size of the window at the time it was changing
DPI, in step 4 above).
## References and Relevant Issues
This message (WM_GETDPISCALEDSIZE) is not widely used, but it is used by
dialogs (user32!CreateDialog), since they also size their windows using
font sizes. The code in this change borrows from the code in the dialog
manager, user32!GetDialogDpiScaledSize.
## Detailed Description of the Pull Request / Additional comments
The WM_GETDPISCALEDSIZE message contains the new DPI and the new size,
which is an in/out parameter. It starts as the new window size, scaled
to the window's current DPI, and is expected to be scaled to the new
DPI.
The client area (the part with the text) is NOT scaled linearly. For
example, if the font at 100% DPI has a height of 7, it could have a
height of 15 at 200%. (And if it did have a height of 14, linearly
scaled, it would surely not be linearly scaled at 150%, since fonts
cannot have a height of 10.5.) To pick the right size, we need to
resolve the font at the new DPI and use its actual size to scale the
client area.
To keep the amount of text in the window the same, we need to remove the
non-client area of the window (caption bars, resize borders, etc). The
non-client area is outside the area with the text, and its size depends
on the window's DPI and window styles. To remove it and add it back, we
need to:
- Reduce the provided window rect size by the non-client size at the
current DPI.
- Scale the client size using the new/old font sizes.
- Expand the final size by the non-client size at the new DPI. 3 天前
3e669029
Oops, it didn't support more than 100 items! 5 天前
旨在为数千万中国开发者提供一个无缝且高效的云端环境，以支持学习、使用和贡献开源项目。
更多推荐
8
0- 0
已为社区贡献43条内容
所有评论(0)