Add Nushell support to venv activation (#3073)

Joseph T. Lyons created 2 years ago

This PR adds an option to run `activate.nu` in the automatic venv
activation code (relevant comment
[here](https://github.com/zed-industries/community/issues/2103#issuecomment-1742355651))

Release Notes:

- Added a `nushell` option to the
`terminal.detect_venv.on.activate_script` setting
([2103](https://github.com/zed-industries/community/issues/2103)).

Change summary

assets/settings/default.json             | 2 +-
crates/project/src/terminals.rs          | 1 +
crates/terminal/src/terminal_settings.rs | 1 +
3 files changed, 3 insertions(+), 1 deletion(-)

Detailed changes

assets/settings/default.json

@@ -361,7 +361,7 @@
           ".venv",
           "venv"
         ],
-        // Can also be 'csh' and 'fish'
+        // Can also be 'csh', 'fish', and `nushell`
         "activate_script": "default"
       }
     }

crates/project/src/terminals.rs

@@ -84,6 +84,7 @@ impl Project {
             terminal_settings::ActivateScript::Default => "activate",
             terminal_settings::ActivateScript::Csh => "activate.csh",
             terminal_settings::ActivateScript::Fish => "activate.fish",
+            terminal_settings::ActivateScript::Nushell => "activate.nu",
         };
 
         for virtual_environment_name in settings.directories {

crates/terminal/src/terminal_settings.rs

@@ -69,6 +69,7 @@ pub enum ActivateScript {
     Default,
     Csh,
     Fish,
+    Nushell,
 }
 
 #[derive(Clone, Debug, Default, Serialize, Deserialize, JsonSchema)]