Leon

> I think it would make sense to split this into 2 PRs. The changes to `rm` (documentation tweaks, a new test) seem unrelated to the larger config change. I...

Well, alright.

@fdncred This is wrong; this PR only changes how the config file is read; the actual structure of `$env.config` remains the same for exactly these compatibility reasons. Eventually they should...

Your comment made me realise I'd had a slight misunderstanding. My apologies. I'd assumed that EngineState (in engine_state.rs) generated the `$env.config` environment variable whenever it was read, so that it...

Problem I just found with this PR: `input` and `output` should be on `$nu.scope.commands` too, because that's supposed to be a superset of `help commands`'s output.

The obvious solution to this is to NOT change `--numbered`, but deprecate it and allow the normal `each` to take 1 or 2-param blocks with no error: OLD: `each -n...

No one's replied, but one of the pull requests where I put this into action got accepted, so I guess that's a very tacit approval?

OK, so like, the problem here is that tables are equivalent to JSON arrays-of-objects (in Nu, lists-of-records). Each record is a row, and the keys of each record are the...

As an addendum, I believe the problem presented in the first post actually calls for a feature like nullable property access, similar to C# and JS's `a?.b?.['c']` syntax. The problem...

Related: #5957