Dan Davison

Would you mind kicking off the CI run here @whitphx?

Hi @whitphx, thanks! I really appreciate the work you've put into this extension -- it's fantastic. The tests did pass on Windows, but I do want to emphasize that there...

Here's an incorrect case (it should kill to end of line in this situation, but the shading shows that it actually kills to the end of the next line) ```python...

And another one, in Scala. Again, this should kill to end of current line only: ``` val userIdInQueryParams = if (satisfiesCustomAccessControlLogic(ctx.key.opaqueName1)) { ```

I agree with that this is a good area to be working on, but I actually don't think that a PR is the right next step here. Here we're having...

> we do have https://github.com/nushell/rfcs Thanks, that looks like exactly what I'm talking about.

> n-th element in Nushell is `get` and slice is `range`. Thank you @kubouch! Updated. (I had been thinking of `get` as for key/column lookups on records/tables, and had not...

> Actually, I've been working on something like this myself in private, but covering the entire basic (non-dataframe non-database) data structure command suite: https://docs.google.com/spreadsheets/d/1Hd6rdMKH1a-ttLsilvFZ0x_Mya7e3aGYBDtSEC6piDI/ This looks great! Do you want...

I think the change is correct (`take` should always return a list; `take 1` shouldn't magically unwrap the result). But seeing as there are other breaking changes we will probably...

As yet another random user disagreement... :) I disagree with the behaviour ``` > [1 2 3] | take 1 ``` IMO this should be an error; in other languages...