Skip to content

Ctags - Neither rebuildOnFileSave nor rebuildOnStart work #793

@obambrough

Description

@obambrough

Environment data

VS Code version: 1.20.1
Python Extension version: 2018.1.0
Python Version: 2.7.14
OS and version: MacOS 10.13.3

Actual behavior

${workspaceFolder}/.vscode/tags file is not updated when I save a python file nor if I restart VS Code.

Expected behavior

${workspaceFolder}/.vscode/tags file will be updated when I save a python file or restart VS Code.

Steps to reproduce:

  • Verify tags file doesn't exist
  • Open a project with python files in VS Code and open a Python source file
  • Verify the tags file still doesn't exist (rebuildOnStart hasn't activated)
  • Make a change to the Python file and save
  • Verify the tags file still doesn't exist (rebuildOnFileSave hasn't activated)
  • Perform a global symbol search
  • The tags file has been created (this is only created if it doesn't exist, if it already existed it isn't updated with new symbols)
  • Add a new function definition to a Python file and save (rebuildOnFileSave hasn't activated)
  • Perform a global symbol search for newly added symbol (this fails to find it)
  • Run 'Python: Build Workspace Symbols' (this updates tags file)
  • Perform a global symbol search for newly added symbol (this succeeds)

Logs

Output from Python output panel (only gets logged when I perform a global symbol search if the tags file doesn't exist, or if I run the 'Python: Build Workspace Symbols' command.)

ctags --options=/XXXXX/.vscode/extensions/ms-python.python-2018.1.0/resources/ctagOptions --languages=Python --exclude=**/site-packages/** --exclude=.history -o /YYYYY/.vscode/tags .

Output from Console window (Help->Developer Tools menu) (I see this on VS Code startup.)

[Extension Host] Python Extension: Failed to get conda info from conda null
t.log @ /Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.main.js:253

Metadata

Metadata

Labels

area-editor-*User-facing catch-allbugIssue identified by VS Code Team member as probable buggood first issue

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions