Jakub Žádník

I just realized you can use `$args` which makes it a Nushell equivalent of `$@`. This makes it actually useful. It's still extremely hacky, but also quite cool. One issue...

Allowing symlinks in the current working directory has recently been allowed: https://github.com/nushell/nushell/pull/12603 https://github.com/nushell/nushell/pull/12749, so I think it should be relatively easy to make `cd` not canonicalize the path.

Yes, I was trying to view some raw hex data and try to see if I can change some bytes. Interestingly, doing `open foo.jpg | first 81` seems to show...

Ah, I'm blind. I'll still keep it open for the unspanned error. Maybe the error could also suggest to call `into binary`.

In my view, block comments fall into the category of “nice to have”, but their complexity and other downsides outweigh their benefits. For example, nesting: ``` ``` Or what if...

I'm fine with this, just one question: Does it affect modules? E.g., what happens if you do `use script.nu; script --foo`?

Since it might take a while until we have a good solution for running scripts with subcommads, we can move forward with it to at least fix the help messages....

Parser should look for files relative to the currently parsed file, but it might be implemented only for modules, i.e., missing for `source`. It should be relatively easy to add...

The problem with this is that programs often exit with a non-zero exit code even when they exit successfully. Some programs expect to be terminated by Ctrl-C. I think throwing...

I don't remember the details, but the Sophia's article highlights the point well. E.g., after running `git diff` of a longer diff, you'd get a shell error reported in the...