Bahex

I'm not 100% sure but I think this was changed way before #15560. As far as I know `break` and `continue` are only supposed to work in actual **blocks** like...

My gut instinct is to keep `break` and `continue` disallowed outside of actual loop blocks: - `each` skips `null` values so a simple `return null` in the closure works as...

Went ahead and wrote the error/exception based version in nu: ```nushell def _continue [] { error make -u {msg: __continue__} } def _break [] { error make -u {msg: __break__}...

Using dark/light agnostic colors by default or detecting the terminal background at launch is good idea. In the meantime you can use the light theme like this: ```nushell use std/config...

Is the problem specifically with the colors of file names from `ls`? Their colors are controlled separately from nushell's config with the `LS_COLORS` environment variable (which is an existing convention...

@weirdan internals actually update it when an error is thrown, the problem here is we can't really detect most errors from uutils and as a result can't throw an error...

This works: ```nushell [foo bar baz] | str join (char -i 0) | fzf --read0 ``` If you need to read `0` delimited strings into nushell you can use: ```nushell...

It's probably safe to deprecate `split-by` now, since `group-by` completely covers its use case. #14337 > Grouping by multiple columns, without `--to-table` returns a nested structure. This is equivalent to...

This is also relevant for `open` and `save`.

`stor` commands are all supposed to affect the global database regardless of the scope. I can't reproduce this issue, the following code works without problem: ```nushell [ { stor create...