Skip to content

Add .vscode workspace config to fix VS Code unresponsiveness - #4

Draft
lukejmorrison with Copilot wants to merge 2 commits into
mainfrom
copilot/debug-vs-code-issues
Draft

Add .vscode workspace config to fix VS Code unresponsiveness#4
lukejmorrison with Copilot wants to merge 2 commits into
mainfrom
copilot/debug-vs-code-issues

Conversation

Copilot AI commented Apr 10, 2026

Copy link
Copy Markdown

Without workspace configuration, VS Code's file watcher, Pylance, and the C/C++ extension scan everything — __pycache__, virtualenvs, CMake build trees, encrypted voice artifacts — causing the editor to freeze in this mixed Python + C++ project.

Changes

  • .vscode/settings.json

    • files.watcherExclude — excludes __pycache__, .venv, dist, build, voices/, and the JUCE CMake build tree from file watching
    • files.exclude — hides compiled artifacts (*.pyc, *.so, __pycache__) from the Explorer
    • search.exclude — skips generated dirs from workspace search
    • python.analysis.exclude — scopes Pylance to project source only
    • cmake.* — points CMake Tools at vst3/juce_venom_starter
    • C_Cpp.* — restricts IntelliSense to VST3 project headers
  • .vscode/extensions.json — recommends Python, Pylance, Black, CMake Tools, C/C++, GitLens, and TOML extensions; VS Code will prompt new contributors to install them automatically

…siveness

Agent-Logs-Url: https://github.com/lukejmorrison/VoiceDNA/sessions/9d959603-5de7-40fe-ae71-65b27fad828f

Co-authored-by: lukejmorrison <7144857+lukejmorrison@users.noreply.github.com>
Copilot AI changed the title [WIP] Investigate unresponsive behavior of VS Code Add .vscode workspace config to fix VS Code unresponsiveness Apr 10, 2026
Copilot AI requested a review from lukejmorrison April 10, 2026 15:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants