Jakub Žádník

OK, cool. Could you also add a test for the `... | take` error so we can track it in the future?

Thanks! I think it's still good to fix the inconsistency. We just had a release and can revise this in subsequent PRs if necessary.

You need to install Python and virtualenv, then create a new virtual environment, then try to source the generated activate.nu and/or deactivate.nu. I'm quite busy nowadays to look into it...

I think this is a good information to add to the help table. My main concern is the table becomes very big. An alternative might be to add it to...

Yeah, I think I overlooked that one. Should be easy to fix.

Yeah, should be easy, check the code for the `use` command in the `nu-commands` crate, that should give your the idea.

Honestly, I don't feel comfortable landing this because you're evaluating the previous pipeline which, apart from side effects like `rm`, could be also something that takes a long time to...

I think it is OK to remove this provided that `let a = {$in > 3}; [1, 2, 5, 6] | where $a` works (it doesn't currently).

You need to split the the PATH by the separator first

Maybe try to expand the path. I think PATH should auto-expand so this might be a bug, but expanding manually should work.