Bahex

Happens with `try` too

Directly using `nu_parser::{parse, flatten_block}` would probably be enough to check for garbage. Though something like `--reject-garbage` could be used in `std/help` too

It's soooo good :heart: Can we add highlighting to the `help aliases` text too?  

Simply wrapping the command in a closure, without even calling it throws the error: ```nushell {|| all-json-path } ``` There might be an issue with the variable capture logic

@frankrefischer while it doesn't solve the variable scoping problem in this issue, `recurse` command introduced in #15840 might cover your use case.

Is there a reason we didn't move ahead with this?

We do have an `Expr::GlobInterpolation` variant, and it actually works... in the specific circumstances where the - command is an external - the bare word interpolation in question doesn't start...

Extra context: - Running as a login shell means the shell process is started with it's `argv[0]` ~set to~ _prepended with_ `-`, e.g. `-/usr/bin/sh`. This can be simulated using the...

Since 0.98.0 (#13785), it's possible to have something like this in `$env.config.hooks.display_output` ```nushell metadata access {|meta| match $meta.content_type? { "application/x-nuscript" | "application/x-nuon" | "text/x-nushell" => { nu-highlight }, "application/json" =>...

This seems to be solved. We can probably add a cookbook entry and close this issue. For anyone who finds this issue before the cookbook entry, here's an example. ```nushell...