Blog

在 VSCode 中安裝了主題和字體之後，開啟折行時，有時會出現折行後仍然有一部分內容需要透過水平滾動條顯示的狀況。

這時候可以進入 VSCode 的設置，檢索”Wrapping Strategy”, 把它設置為 advanced 即可。

Have you ever encountered a frustrating situation where your browser can access a local service, but your terminal and IDE cannot? Recently, I faced this exact issue while trying to access a ComfyUI API running on 127.0.0.1:8188.

The Problem

• What worked: Browser with proxy settings could access the local service
• What didn’t work: VSCode, terminal, and curl commands couldn’t reach 127.0.0.1:8188
• What I tried: Cleared system and IDE proxy settings, removed HTTP_PROXY and HTTPS_PROXY environment variables

Despite confirming that echo %HTTP_PROXY% and echo %HTTPS_PROXY% returned empty values, the issue persisted.

The Solution: Let Your Tools Tell You What They See

Sometimes the best approach is to let your applications reveal their own proxy configuration. Here’s a Python script that helped me diagnose the issue:

import os
import urllib.request

print("--- Checking Environment Variables from Python's perspective ---")
# os.environ is how Python sees all environment variables
print(f"HTTP_PROXY: {os.environ.get('HTTP_PROXY')}")
print(f"HTTPS_PROXY: {os.environ.get('HTTPS_PROXY')}")

print("\n--- Checking what proxies urllib automatically detects ---")
# getproxies() shows what urllib will use by default
print(urllib.request.getproxies())

What This Reveals

The urllib.request.getproxies() function shows you exactly what proxy settings your Python environment detects, even when environment variables appear clean. This often reveals:

• Registry-based proxy settings (Windows)
• System-wide proxy configurations
• Application-specific proxy settings that override environment variables

The Fix: Explicitly Disable Proxies

If you find unwanted proxy settings, you can force urllib (and applications that use it) to bypass proxies entirely:

# Create a proxy handler with no proxies
proxy_handler = urllib.request.ProxyHandler({})
opener = urllib.request.build_opener(proxy_handler)
urllib.request.install_opener(opener)

Key Takeaway

When troubleshooting network connectivity issues, don’t just rely on environment variables and system settings. Use your application’s own introspection capabilities to understand what it actually sees. This approach often reveals hidden proxy configurations that standard troubleshooting methods miss.

Pro tip: Always check what your specific tools and libraries detect, not just what the system claims to be configured.

If you’re experiencing issues with VSCode where clicking the “Run” button in the top-right corner of a Python file doesn’t work properly, you might encounter these problems:

1. No new terminal window is activated (the new windows are created in the background)
2. The command “python xxx.py” doesn’t execute automatically

Here’s a quick fix that often resolves this issue:

Solution:

Go to your VSCode Extensions panel and locate the Python extension. Check if you’re currently using the pre-release version of the Python extension. If you see “Pre-Release” indicated next to the Python extension, that’s likely the culprit.

Simply switch from the pre-release version back to the stable release version. You can do this by clicking on the extension and selecting the option to install the release version instead.

After switching to the release version, restart VSCode and try running your Python file again. The run button should now properly activate a new terminal and execute your Python script as expected.

If you find that your Clash Verge + Proxifier setup only proxies part of your traffic, double-check whether the port opened from Clash Verge to Proxifier is set to Mixed Port or another type. If it is not set to Mixed Port, change it to Mixed Port, and it should work.

This issue can occur with VS Code and GitHub VS Code.

On the other hand, for VS Code and Docker, if you are using Proxifier, please change your “localhost” proxy rule to Direct instead of Proxy.