Ian Manske

This PR makes use of `reedline`'s external printer feature. As such, there is a [companion PR](https://github.com/nushell/reedline/pull/737) there to flush out that feature and mark it as no longer experimental. Also,...

@WindSoilder thanks for the feedback! > I think it's good to report additional information in a record. Makes sense, will work on that! > Yup, I think once we press...

The original plan was to later generalize this to closures instead of only allowing a single external command. Since the external printer with reedline seems to be a little tricky...

Yep, I'm not surprised lol. The step value is a forgotten child. I think we can keep this open, but some related issues: - #11521 - #11086 (thanks for starting...

Yeah, that is for sure one reason. In many commands, argument ranges are used to signify a slice range. Places like `nu_cmd_base::util::process_range` assume this and ignore the step value. I'm...

@KAAtheWiseGit if you want to, then yeah thanks! I hastily rebased some [old code](https://github.com/IanManske/nushell/tree/number-range) in case you find it helpful. Ignore that I made `start` type `T` instead of `Bound`...

Yeah, I had considered this as well. I'm currently on the fence about it. On one hand, the issues you linked shouldn't be too hard to solve. For example, the...

> Design question No. 1: how should this handle negatives on streams? Good question. I think there's a possible solution using the Rust std lib `VecDeque` (keep the last n...

Thanks for explaining, I remember part of the issue now. `select` should be preserving the structure of the data; it can be though of as a filter or mask over...

> Is there a write somewhere on the Nushell's new benchmarking system? I'm not sure. The benchmarks are still somewhat being figured out (e.g. #12469, #12384, and the original PR...