From a46c21cffb6de32fe65292380f8452cf6ab442ba Mon Sep 17 00:00:00 2001 From: Darren Schroeder <343840+fdncred@users.noreply.github.com> Date: Sun, 3 Sep 2023 19:19:04 -0500 Subject: [PATCH] add plugin path when there are no signatures (#10201) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit # Description This PR adds the ability to have a `$nu.plugin-path` even when you plugins are registered and it also should work with `nu -n --no-stdlib`. ### Before It would give an error ``` │ plugin-path │ IOError("Could not get plugin signature location") │ ``` ### After It returns the proper path, like this for me ``` │ plugin-path │ /Users/fdncred/Library/Application Support/nushell/plugin.nu │ ``` Closed #10198 # User-Facing Changes # Tests + Formatting # After Submitting --- crates/nu-protocol/src/eval_const.rs | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/crates/nu-protocol/src/eval_const.rs b/crates/nu-protocol/src/eval_const.rs index 6cb8e13e5b..f2fc2a6571 100644 --- a/crates/nu-protocol/src/eval_const.rs +++ b/crates/nu-protocol/src/eval_const.rs @@ -113,6 +113,11 @@ pub fn create_nu_constant(engine_state: &EngineState, span: Span) -> Result