Stefan Holderbach

Good point about unpredictable runtime by @kubouch. Definitely props to @nibon7 for giving this a shot. I think to have acceptable safety and speed we probably have to do this...

Sounds reasonable to me, don't know if there are specific uses of this feature. Might have been superseded by some of @kubouch 's work in getting the role of blocks...

Amazing sleuthing! You are like the human version of a fuzzer :D

Maybe we should add `let` to the minimal `Example` testing environment. (same general comment as in https://github.com/nushell/nushell/issues/7032#issuecomment-1306225196) https://github.com/nushell/nushell/blob/3d8d7787ded739935996b407156174ef9b835b1d/crates/nu-command/src/example_test.rs#L27-L58

The environment in which the `Example`s are run is restricted to the command under test and some meager core commands. https://github.com/nushell/nushell/blob/3d8d7787ded739935996b407156174ef9b835b1d/crates/nu-command/src/example_test.rs#L27-L58 I think the original reasoning was that the startup...

The `Into` and `From` in this list are in and of itself useless in this context as they are the meta commands that will just display the help message referring...

I think this points to a larger issue we have: we have our own glob implementation in `nu-glob` used in the filesystem commands (`ls` etc. and in this case `watch`)...

Definitively an interesting enhancement! You really get a hang of the code base! Do you have some before and after code samples for the PR description to make it easier...

> an `enumerate` command (used like `ls | enumerate | where ...`) would be worse than the current `-n` behaviour, as it would explicitly change the input into something like...

We discussed in todays team meeting on [Discord](https://discord.gg/NtAbbGn) that this is good to land (sending the help message down the pipe just causes problems). We just need to make sure...