VSCode 1.20.1中“工作区中转到符号”功能失效求助

Let’s start by aligning on your scenario: you’re using VSCode 1.20.1, have ctags installed via brew install ctags, your virtualenv’s python.pythonPath is configured correctly, "Go to Symbol in File" works flawlessly, but "Go to Symbol in Workspace" fails to pick up some symbols. You’ve identified that the .vscode/tags file wasn’t updating—deleting it and forcing a rebuild fixes the issue, and you can reproduce this with a two-file project.

Here’s how to address this reliably, plus context on why it’s happening:

1. Manual Workspace Symbols Rebuild (Immediate Fix) #

Since you already saw deleting the .vscode/tags file works, here’s the full repeatable workflow:

• Navigate to your project’s root directory, find and delete the .vscode/tags file (you can do this via terminal with rm .vscode/tags or directly in VSCode’s file explorer)
• Open the command panel (Cmd+Shift+P on Mac, Ctrl+Shift+P on Windows/Linux) and search for Rebuild Workspace Symbols to trigger a fresh index
• Alternatively, restart VSCode—it will automatically rebuild the tags file on launch if it’s missing

The .vscode/tags file stores the workspace-wide symbol index VSCode uses for "Go to Symbol in Workspace". When this file gets stuck (and doesn’t update as you add/modify files), it leads to missing symbols.

2. Verify Ctags Configuration & Compatibility #

Even though you installed ctags via brew, double-check these to rule out underlying issues:

• Run ctags --version in your terminal to confirm you have a compatible version (VSCode 1.20.1 works best with universal-ctags, which brew installs by default)
• In VSCode settings, search for ctags.path and ensure it points to your brew-installed ctags executable. For Intel Macs, this is usually /usr/local/bin/ctags; for Apple Silicon, it’s /opt/homebrew/bin/ctags

3. Check Workspace Exclusion Rules (For Two-File Repro) #

Since you can reproduce this with a two-file project, make sure neither file is being excluded from indexing:

• Open .vscode/settings.json in your project
• Look for files.exclude and search.exclude sections—ensure your project files aren’t listed here (VSCode won’t index excluded files, so their symbols won’t show up in workspace searches)
• Also confirm your virtualenv is correctly selected: open the command panel, run Python: Select Interpreter, and pick your project’s virtualenv (this ensures VSCode uses the right Python context for symbol parsing)

Why This Happens #

VSCode 1.20.1 has a known quirk in its workspace symbol indexing logic—sometimes, the auto-update trigger for the .vscode/tags file fails when working with small projects (like your two-file setup) or when files are modified quickly. This bug was addressed in later VSCode versions, but if you’re stuck on 1.20.1, the manual rebuild workaround is the most reliable fix.

内容的提问来源于stack exchange，提问作者William