Douglas

As a workaround (for some use-cases, but perhaps not all), something like `ls ./~` will disambiguate and allow access to the file, rather than interpreting it as "HOME".

Of course, *other* Nushell commands can output to stderr. I just noticed in my history the (expected): > `Warning: The first row contains a null value, which has an unknown...

@sholderbach I understand your reasoning there, but is redirection of internal Nu commands really tied to the decision of *what* is doing the "sending" to stdout/stderr? This *seems* to me...

@fdncred It's in the linux-utils package, I believe. Err, maybe `util-inux` in Ubuntu. I just installed it in a Nix-shell to test. But yeah - I shared your confusion when...

Ah yeah, this brings back memories of trying to get Alacritty running in WSL with Nix ... I never was successful. It's not Alacritty's fault - Nix Shell (or maybe...

@fdncred and @zhiburt Apologies for the delay responding, but yes, I just built with the change from #11905 and it now returns the expected results. Thank you!

I haven't been able to reproduce this with the default plugins. For instance `'register nu_plugin_custom_values.exe' | nu-highlight` just returns the syntax-highlighted string. I haven't tested with procmon yet, but running...

Ok, now that I can repro. But from my previous testing, it's even more odd: * Registering a default plugin just doesn't (seem to) trigger the registration at all --...

I get your point, but I'm not sure I agree with the conclusion, at least not as a blanket rule. Some of these are most definitely intended for end-user use,...

As a nice alternative, perhaps change all of them to be ` ...(rest)` but detect if `` is a list and automatically handle it if so.