1

Problem:
When creating a new terminal in VSCode (v1.102), it automatically enters the base environment and then automatically executes commands:

D:/Anaconda/Scripts/activate
conda activate ML

causing:

Visible cmd terminal flash
5-10 second startup delay
Occasional freezes

Expected Behavior:

Direct opening in ML environment (instant) without visible commands.

Troubleshooting Attempted:

Toggled python.terminal.activateEnvironment (true/false)
Downgraded to VS Code v1.85 (issue persists)

System & Extension Details:

OS: Windows 11
Conda: v24.11.3 (path: D:/Anaconda)

Explicit Question: What configuration (VSCode/Conda) will open terminals directly in ML without visible activation sequences?

this is my setting.json:

    `{
    "terminal.integrated.profiles.windows": {
        "PowerShell": {
            "source": "PowerShell",
            "icon": "terminal-powershell"
        },
        "Command Prompt": {
            "path": [
                "${env:windir}\\Sysnative\\cmd.exe",
                "${env:windir}\\System32\\cmd.exe"
            ],
            "args": [],
            "icon": "terminal-cmd"
        },
        "Git Bash": {
            "source": "Git Bash"
        },
        "Windows PowerShell": {
            "path": "C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\powershell.exe"
        }
    },
    "terminal.integrated.defaultProfile.windows": "PowerShell",
    "workbench.settings.applyToAllProfiles": [
        
    ]
}`
New contributor
user31189378 is a new contributor to this site. Take care in asking for clarification, commenting, and answering. Check out our Code of Conduct.

0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.