Darren Schroeder

Did you try the suggestions I gave in the /r/nushell?

Maybe a gif that demonstrates what you're seeing would help. (ok, i see the pictures now) I'm not sure what you mean under your completeness point. `ansi esc` is not...

starting position  after running the `clear` command  after running the `ansi cls` command  after running the `ansi clsb` command  after running the `$"(ansi esc)c"` command ...

> My expectation is that the clear command should work like the clsterm or cls2 or $"(ansi esc)c". As in, it should both clear the screen, and remove everything that...

You can write your own `clearall` custom command. I'm not sure why we need to add something else?

I would not support adding a new command but I could see adding a parameter like `clear --all` to clear the screen and the back buffer. Crossterm has that functionality...

Agreed, it shouldn't crash but I also didn't think it supported time, hence the name `seq date`. Below, `next` is a `NaiveDate` and not a datetime. https://github.com/nushell/nushell/blob/d1c807230b4f35a9d963ce6fee5b72641690fe06/crates/nu-command/src/generators/seq_date.rs#L317-L326

That's what I was seeing too since it's a NaiveDate vs a NaiveDateTime.

Looking at this again, it seems like this could be prevented if we just check the `--output-format` and don't allow %H %M %S things. I'm also good with trying the...

This seems to work fine though `^-what?`