Wind

Maybe you can use `nu_repl_code` to test auto-cd?

> I wonder what its original purpose was? There are some issues that only happened in repl, I guess that's the reason to use `nu_repl` to test such case

I have the same concern about turning the exit codes into `ShellError` variants. I remember @elferherrera and @sophiajt had voted against it before: https://github.com/nushell/nushell/pull/6079#issuecomment-1189168717, https://github.com/nushell/nushell/pull/6079#issuecomment-1189518033

Well, `unexpected_eof` is the key to allow multi-line string. You can define a function like this: ```nushell def func [] { { "A": ""B" #

I don't think it's a breaking change because it converts from a required parameter to optional parameter, so I will remove the label

I think we also need to change parser, it uses `collect` command to build `$in` variable (at line 6249). https://github.com/nushell/nushell/blob/92831d7efcd0586a85966560beb0c538f4a0fc36/crates/nu-parser/src/parser.rs#L6241-L6255

I'm not sure about it either. Because sometimes it's easy to do something like this: `"aaa" o> file.txt`, which is shorter than `"aaa" | save -fw file.txt`

Yeah, it's definitely the `complete`'s issue. I remember it's not easy to fix before https://github.com/nushell/nushell/pull/11934 pr. Not sure if the situation has changed. I can try to look into this.

Maybe we can introduce a new `prelude` module, currently `std` is implemented in nushell. And I don't think mixing `std` and new commands after `1.0` is a good idea. We...

> 1. Add a new Value::Glob variant which could be passed around and cast to/from string (into string, into glob) to prevent glob expansion or collected into a list if...