Jakub Žádník

You can do also `with-env { PWD: ... } { nu }`

`PWD=C:\ nu` works for me from Nushell as well. It doesn't in Powershell but I have no clue how Powershell works.

Oh, oops, this is not meant to be closed. The error might be in the parser collecting the captures, I'm not sure.

Interestingly, this does not throw an error: ``` > ls *.json | each {|it| open $it | get s } | save output.csv ``` but this does: ``` > ls...

Entries are added to history after the command gets executed, that makes sense to me. What are you trying to achieve?

So when you run a command, like `git status`, before it executes, bash stores "git status" in `BASH_COMMAND` variable? I wanted to know how you would use this feature. What...

I couldn't get it working with the `RAYON_NUM_THREADS`, even spawning a new `nu` process with this env var set (using `stress --cpu 1` to get 100% load so it's easy...

I'm thinking, instead of adding new syntax shapes, we should maybe write internal custom completions. So for `help` we would write the equivalent of `def help-complete [] { help commands...

OK, that makes sense and actually does not contradict what I wrote earlier -- both things can exist at the same time. I think this PR shouldn't hurt anything but...

So, I think fixing the completions to prioritize files over commands is useful, but adding a new flat shape for commands is not very useful. Consider this ``` def foo...