nushell: mise.nu breaks path completion

[deas]

Describe the bug
Following nushell configuration breaks path completion
A clear and concise description of what the bug is.

To Reproduce
Use a system without default nushell configuration, such that executing nu creates initial configuration files in ~/.config/nushell. In nu, ensure that completion works for binaries.

e.g. I have qemu installed. Hence, typing qemu-<TAB show various binary execution completions.

❯ | qemu-
qemu-io                     qemu-nbd                    qemu-img                    qemu-pr-helper              
qemu-system-arm             qemu-system-i386            qemu-system-armel           qemu-system-armhf           
qemu-system-amd64           qemu-system-arm64           qemu-system-x86_64          qemu-storage-daemon         
qemu-system-aarch64         qemu-system-x86_64-spice    qemu-system-x86_64-microvm  

Now do as per docs:

'
let mise_path = $nu.default-config-dir | path join mise.nu
^mise activate nu | save $mise_path --force
' | save $nu.env-path --append
"\nuse mise.nu" | save $nu.config-path --append

Start a new nu shell process. The completion no longer works.

Expected behavior
Completion working after adding mise configuration to nushell.

mise doctor output

n/a

Additional context

❯ nu --version
0.96.1

[deas]

Meanwhile, I found a workaround. There may be a more elegant way, but it should probably be emitted by mise activate nu.

def --env "update-env" [] {
  for $var in $in {
    if $var.op == "set" {
      # The following tow lines work around the issue
      let val = if $var.name == "PATH" { $var.value | split row (char esep) } else { $var.value }
      load-env {($var.name): $val}
    } else if $var.op == "hide" {
      hide-env $var.name
    }
  }
}

[last-partizan]

Yes, this fix works, thanks!

[last-partizan]

@jdx it think it's a bug and should be fixed in mise.

I can make a patch with required changes. Or do you think it works as expected?