Andrej Kolčin

Design question No. 2: use strings instead of cell paths in `select` and `reject`? The reason for this is because this forbids nested cell paths anyways, since we'll have `get`...

Oh, and I also found a bug in ranges: #11769 So `propose select` can't be used to skip every nth row yet.

@IanManske re cell paths: I didn't think at all about `reject`. Currently select supports nested cell paths, but only without rows, and it also converts the name in an somewhat...

Added a new `propose reject` prototype. The code is a mess for now, but the architecture enabled the following new features: - Using ranges. - Handling binaries. - Handling infinite...

@fdncred ```Nushell Error: × Config record contains invalid values or unknown settings Error: × Error while applying config changes ╭─[/home/kaathewise/.config/nushell/config.nu:254:1] 254 │ 255 │ use_ls_colors: true · ──┬─ · ╰──...

I thought it might've been a Neovim-specific thing, but I can't replicate it with `gopls` or Rust analyzer.

[Ian's](https://github.com/IanManske/nushell/tree/number-range): fixed

[Ian's](https://github.com/IanManske/nushell/tree/number-range): fixed

[Ian's](https://github.com/IanManske/nushell/tree/number-range): fixed, same error as `10..1..11`

[Ian's](https://github.com/IanManske/nushell/tree/number-range): - `9_223_372_136_854_771_000..10000000000000000000` works fine. - `10000000000000000000..10000000000000000000` outputs the value 1024 because floating point precision.