Leon

> I'm missing the point here. Why do we now have two parameters `-p` and `-s`? Why can't `-i` suffice? Well, consider this (using GNU `false` representing a command with...

I notice in [this pull request](https://github.com/nushell/nushell.github.io/pull/656/commits/55484dfb610026f1071210fa993bce6df7967c1e#diff-91a0d74f8f7c2086dfd191891820be814d9e984bd1067725797d62c237dd5b4fR142) that there's an intent(?) to add Bash `&&` and `||` style pipeline operators in 0.80. Those sound like they'd fit this use-case better (although...

`describe` is not the correct place for command descriptions. That is what `help` is for. `describe` seems(?) to be the language's equivalent of ~~JS's `typeof`~~ Python's `type()` - a service...

I'd like it if the person who actually originally implemented this command could be brought in to give a statement of intent, just to be sure.

I think the real bug here is that running `from csv` on a non-text pipe gives *literally no error whatsoever*.

My opinion is that the `split` commands simply shouldn't iterate over `list`, instead requiring explicit `each` to do so: ``` 〉['aa' 'bb'] | each {split chars} | to nuon [[a,...

To be clear, the motivation for this idea is to make `ls` easier to use as a pipeline-starter, and having all of the columns on the table means you don't...

I imagine that, as a solution, the default `table` view would be made to truncate it (similar to how other long tables are truncated) but in a special `ls`-specific way...

If there's a performance reason for leaving these other columns off by default, then I understand completely.

Sorry, I misworded that message. I meant all of these: ``` 〉[1 2 3] | each { print $in } | print 'Done' Done 〉[1 2 3] | for i...