Wind
Wind
Closing the issue because the question is answered.
It's happened after this pr: #16912
Personally I'd like to hang it as well, because `polars-parquet` still depends on 5.0. We can wait until it's ok to update `polars` dependencies
Thanks for proposing the PR. I think it's too old and still a draft PR. I'm going to close it. If you think the change is still necessary, feel free...
I get the same issue, when I tried to run ` cargo test --workspace --exclude nu_plugin_*`, the test failed
Hi, thank you for the pr! But personally I'm not sure if we want such feature yet. Additionally It can be implemented as a plugin command easily.
Sorry we didn't document it. We want users to be able to use custom command flags like "foo --hi-there" normally. But in case of variable usage, since we are not...
Closing the issue because the question is answered.
Hmm, I run nu shell on Win11, wsl2, windows terminal, and I can't reproduce it: ``` ❯ timeit { nu-0.109.1-x86_64-unknown-linux-gnu/nu -n --no-std-lib -c '{ ...(version) startup:$nu.startup-time } | print; exit'...
I think it's fixed by #17186 and #17085 it's ok to close it :)