Jakub Žádník

You can currently work around this by aliasing the original command beforehand: ```nushell alias old-cd = cd def-env cd [path] { old-cd $path print 'foo' } ```

This is actually not a Nushell problem, but just the completion definition was written such that it requires the positional argument instead of making it optional. Changing ``` command: string@"nu-complete...

The issue is worded such that it sounds `npm`-specific. https://github.com/nushell/nushell/pull/7527 will be merged in after the 0.73 release, you're welcome to try it and see if it helps. Unfortunately, "commands...

The `command` should be optional: `command?`.

This sounds like Nushell is having trouble with interactive, "prompt-style" commands. I also noticed, when Nushell is launched from Bash (i.e., not a default shell), exiting back to Bash locks...

I cannot reproduce the original issue (maybe because I have the password prompt disabled with `sudo`) but the `su | foo bar` issue is still present.

```nushell let o = ["path" "name" "size" "hash"] 'test.nu,test.nu,67 B,55E7' | split column ',' ...$o ``` seems to work now.

Error message: ``` thread 'main' panicked at 'Can't create a Span whose end < start, start=18446744073709551598, end=1', C:\Users\kubouch\.cargo\registry\src\github.com-1ecc6299db9ec823\reedline-0.14.0\src\completion\base.rs:18:9 ```

Cool, thanks for digging in! It might be the cursor position but I haven't worked on the completions code, I'm not sure. You might need to backtrack the function and...

I have no idea either. I had the same problem caused by allowing profiling of pipeline elements https://github.com/nushell/nushell/pull/7854 and solved it by boxing the metadata. You can try if the...