terminal.profiles issues and how-to

Answered

Hi,

I started to tryout Fleet yersterday. I've setup a small python workspace. My python interpreter points to the local venv that I've created at the root of that workspace.

Now I was trying to setup a `terminal.profiles` so that my virtual env gets source every time I open a new terminal window. Tried to do the following:
```
    "terminal.profiles": [
        {
            "program": "powershell.exe",
            "args": [".\venv\Scripts\Activate.ps1"],
            "name": "powershell test"
        }
    ]
```

...and wanted to test it, but I can find any reference or trigger for this new profile `powershell test`.

I'm on windows 11 by the way.

Thanks in advance, cheers

0
2 comments

but I can find any reference or trigger for this new profile `powershell test`.

There is no profiles management currently. We will implement it in scope of

FL-13186 Design a chooser for terminal profile settings

request soon (the current plan is to implement it in 1.13 version).

Also for the auto activating of venv in terminal we have this request:

FL-10630 Auto-activate virtual environment in the built-in terminal

0

Thanks for the quick answers

Cheers

0

Please sign in to leave a comment.