zc he

I think we can on hold the cleansing task since it's a breaking change that won't bring much benefit. But this thread can be used to keep track of the...

@Beinsezii no longer the case in nu 0.102 on my machine, could please help to confirm?

@Beinsezii https://github.com/user-attachments/assets/e4594533-f692-4445-9916-2c529825fb8c Is this what you're expecting, or do you mean something else? Here's my `$env.config.completions`, FYI |sort|case_sensitive|quick|partial|algorithm|external|use_ls_colors| |-|-|-|-|-|-|-| |smart|false|true|true|prefix|{enable: true, max_results: 100, completer: closure_788}|true|

> @blindFS Yes, that's what should happen. You must be using Carapace. Use any of the other closures from the cookbook and it will fail to complete properly. Nope, start...

@Beinsezii first of all, you should be aware that nushell completions treat `start` and `mpv` differently (internal vs external). And the file completion shown in my screenshot is the fallback...

> It treats `start` and `mpv` the exact same, as they both use general `string` completion Could you please provide a minimal reproducible config file then?

> Try it yourself > > ``` > # From https://www.nushell.sh/cookbook/external_completers.html#external-completers > let fish_completer = {|spans| > fish --command $'complete "--do-complete=($spans | str join " ")"' > | from tsv...

> I have no idea how much more clear I can make it that `start` and `mpv` are completed the same way because they both use the string data type....

> Seems like both of those should be `where condition == true` vs just `where condition` but maybe it's a bug in nushell? I'm not sure, that usage is not...

> I think the problem here is the way the row condition shorthand is expanded, we only expand the shorthand on the left side. Like it might be confusing if...