Dan Davison

Yes, I was surprised when I saw that many nushell commands vectorize automatically over input lists. My initial reaction was that no commands should do that since nushell has `each`,...

I'm not sure there's a bug or feature request here. The problem is fairly specialized: it's essentially > There's a list of records (which have one key and an integer...

Without expressing an opinion for or against, I just want to say that one other possibility would be to remove `size` and `modified` from default `ls` output so the command...

@fdncred this issue is a design discussion: > I think the -l flag is one which ls doesn't really need (and kind of muddies the simplicity of Nushell by serving...

Ah right, yes I think this was a design proposal -- I don't think the author was looking for a personal solution (I think they know how to do that).

> My main concern is the table becomes very big. An alternative might be to add it to `$nu.scope.commands` instead. Thanks @kubouch. I agree that we don't want the table...

Thanks for thinking about this @merelymyself; > How might this work out when you have a command which has multiple possible outputs? first x returns a list but first returns...

> I'm also wondering about the inverse of this; does this approach rule out commands with multiple possible input types? The way I'm thinking about this is that we can...

> One example may be sort. Sort should work with ints, strings, other types? Sort is a bit different -- it works on `list` for various sortable `T`, and that's...

> We haven't decided on the future of command overloading, but: > If we remove command overloading: we remove input/output types @rgwood I think that the "cell paths" feature in...