🤦 This was me setting detect_venv as a top-level option, instead of terminal.detect_venv.

I believe that the default option should auto-detect the user's login shell instead of just sourcing .venv/bin/activate.
I understand that the activation script can be explicitly set to fish , csh or nushell but this only works if all team members working on the project use the same shell.

If that is not a common enough scenario to implement it, then can someone suggest an alternative way? Is there a way to call a shell script when a terminal starts?

I believe that the default option should auto-detect the user's login shell instead of just sourcing .venv/bin/activate.

#11246 covers this.

I understand that the activation script can be explicitly set to fish , csh or nushell but this only works if all team members working on the project use the same shell.

@iteroji How are you sharing your Zed config with other team members? That's not an expected use case -- your Zed config should be local to you only.

@iteroji How are you sharing your Zed config with other team members? That's not an expected use case -- your Zed config should be local to you only.

I'm sharing the project settings as part of the project repo, not the global settings. Can I partially override global settings, such as the directories in detect_env? Because in that case it would be easier to leave the activation_script out of the project settings, and only override the directories part.

I'm sharing the project settings as part of the project repo, not the global settings. Can I partially override global settings, such as the directories in detect_env? Because in that case it would be easier to leave the activation_script out of the project settings, and only override the directories part.

Oh, I see. I didn't think about that use case at all.

You should probably open a separate issue for that.