Darren Schroeder

Thanks for this. It's unfortunate that polars panics. I've seen PRs with catch_unwind type behavior before and we generally do not allow that, but I'll let other team members chime...

We decided against panic hooks recently. I'm wondering if something can be landed upstream? Or even if the latest polars, which we are not on yet, fixes this?

right but we probably don't want to have a panic hook for every possible crate we use. Is there a global way to catch all these in a graceful manner...

> It currently looks like Command::run is called at various places. Those could be wrapped by one function for executing a command. Then catch_unwind could be handled there. Also, maybe...

That's a crazy test case, but you're right, even though it's invalid, it still shouldn't crash nushell.

I figured it out, yay me! ```nushell ❯ $cities | where info.0.pop == 55 ╭#┬─city──┬────info─────╮ │0│NewYork│[table 1 row]│ ╰─┴───────┴─────────────╯ ❯ $cities | where info.0.pop == 55 | table -e ╭#┬─city──┬────info─────╮...

I don't believe the intent of `where` is to search all rows in a nested table. I think it's supposed to search all rows for a particular column. I think...

To filter on a table with nested tables, I can see filtering by the inner table or the outer table, but not both without specifying two filters, one for inner...

There's a setting in the config.nu ```nushell display_output: "if (term size).columns >= 100 { table -e } else { table }" # run to display the output of a pipeline...

There is no border-radius. There are only table modes/themes. ```nushell table --list | each {|r| print ($r); print (ls | first 3 | table --theme $r)} ```