Dan Davison

I think you're right @webbedspace that, as @fdncred says, command names are not currently named or grouped in a very logical way. It should be a really nice improvement to...

> `detect columns` is more closely related to `from ssv` I see, thanks. Do you remember why the decision was taken not to expose the functionality under the `from` command,...

Thanks @fdncred, I see what `detect columns` does now. It is really useful -- e.g. I used it here: https://github.com/nushell/nu_scripts/tree/main/network/sockets @webbedspace I agree that "detect columns" doesn't feel like the...

> `from ssv` just doesn't say to me that we want to take some human readable columnar output and transform it to nushell tables. Right, good point, I can see...

I think: - We should not do this renaming right now, but it's good to discuss how we think things should be named, including things that already have names. -...

I agree that `format` is a tempting counterpart to `parse`, for two families of nushell commands that do `structured -> string` and `string -> structured` respectively, and I agree that...

I really appreciate this write-up. I agree with the sentiment (that input and output types need to be much better documented) and I think that the proposed format is really...

[ansitok](https://gitlab.com/zhiburt/ansitok/-/blob/master/src/parse/ansi_parser.rs) now uses [utilities](https://github.com/dandavison/delta/tree/master/src/ansi) built on the VTE state machine iterator from delta, which is well-tested for a couple of years in delta, and does no allocations in the state...

> Consolidating the like 5 different ANSI crates in nushell should be a good goal. Haha :) Cool, I think we're saying the same thing!

This applies to `split row` also (is there a difference between `split chars` and `split row ''`?)