Darren Schroeder

I also don't like how `shells --help` lists `show` in the usage above. If I had my way, it would look more like this. ```nushell ❯ shells --help Display current...

> Oddly, the officials docs pages for [dexit](https://web.archive.org/web/20240701020248/https://www.nushell.sh/commands/docs/dexit.html) and [enter](https://web.archive.org/web/20231211031608/https://www.nushell.sh/commands/docs/enter.html) on the Wayback Machine). Example screenshots showing the resolved drop and add commands in the Usage section[1](https://github.com/nushell/nushell/issues/13151#user-content-fn-1-fe2562bad21d041afe9ac38a0e491892): I'm guessing that...

Nushell uses rust strings which are utf-8 already so there's no need to change anything in nushell to get utf-8.

So, that means your question is how to set your terminal to 65001 every time. I've googled it before and that's what I did for my Windows machine. So I...

One last point of clarification, `chcp` is a Windows command and doesn't change anything that nushell does. It changes the active code page in Winodws which can enable Windows to...

We talked about this recently and seems like having a closure parameter to `split list` would be a good idea.

We would accept a PR to fix this. I have no idea what's going on here.

We use canonicalize pretty heavily, so that may be the problem.

@devyn Have you seen this? Maybe it's a better approach? https://github.com/nushell/nushell/discussions/12978

I don't see the inconsistency but maybe I'm missing the point. I think it's the semicolon that's throwing you off. That changes what the command is doing. You are telling...