terminal.integrated.defaultProfile and terminal.integrated.automationProfile behaves differently

See original GitHub issue

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.64.0-insider (user setup)
  • OS Version: Windows_NT x64 10.0.19044

I can define my preferred terminal profile using the terminal.integrated.profiles.linux setting:

    "terminal.integrated.profiles.linux": {
        "zsh": {
            "path": "zsh",
            "args": [
                "--login"
            ],
            "env": {
                "TMUX": "false"
            }
        }
    },

…and I can specify this profile (referring to it by name) as my defaultProfile:

    "terminal.integrated.defaultProfile.linux": "zsh",

So this works fine for the standard built-in Terminal in VS Code.

However, I also want to use this terminal profile in the debugging-terminals. And according to the documentation, the setting terminal.integrated.automationProfile.linux should work like the terminal.integrated.defaultProfile.linux, allowing me to specify:

    "terminal.integrated.automationProfile.linux": "zsh",

But this does NOT work. The setting terminal.integrated.automationProfile.linux expects a dictionary/object like the terminal.integrated.profiles setting. But it only accepts keywords path and icon, so I’m not able to specify the args and env that I need.

Proposed fix: Make sure terminal.integrated.automationProfile behaves like terminal.integrated.defaultProfile (and according to the documentation), allowing us to specify a profile name defined in the terminal.integrated.profiles setting.

Issue Analytics

  • State:open
  • Created 2 years ago
  • Reactions:19
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

3reactions
codarchcommented, Apr 2, 2022

I have the same problem (on Windows 10 using Visual Studio Code 1.66.0) and in my opinion it is more of a bug than a feature request.

Based on the naming and description I would expect terminal.integrated.automationProfile to behave the same as the terminal.integrated.defaultProfile setting (that is, it should be set to a profile name defined under terminal.integrated.profiles). But I cannot even provide a dictionary/object to it, because when I try to do so, I receive the following message from Visual Studio Code: Incorrect type. Expected “null”.

So it just seems to be impossible to use the terminal.integrated.automationProfile at all.

0reactions
bernardofmcommented, Jun 29, 2022

Similar same problem here. I need to configure the env variables for automation profile to use with attach debugger.

The automation profile only works for tasks with the setting:

"type": "shell"

When launch the debugger, the automation profile env do not work at all.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Terminal Profiles in Visual Studio Code
Visual Studio Code's integrated terminal allows configuring various profiles to make launching various shells easier.
Read more >
How to change the integrated terminal in Visual Studio code
To change the integrated terminal on Windows, you just need to change the terminal.integrated.shell.windows line: Open VS User Settings (Preferences > User ...
Read more >
Integrated terminal - vscode-docs1
Managing Multiple Terminals. You can create multiple terminals open to different locations and easily navigate between them. Terminal instances can be added by ......
Read more >
VSCode 所有的默认配置项 - CSDN博客
vscode.image-preview: Provides VS Code's built-in image preview ... is by creating a terminal automation profile with `terminal.integrated.
Read more >
Problem with deprecated settings for integrated terminal - Reddit
defaultProfile.windows": "Git Bash", }. However, every time I restart VSCode, my integrated terminal is reset to PowerShell.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found