Additional clip copy options

[NotTheDr01ds]

Proposal for #1009:

• Passes complex values through table -e to render properly
• By default, strips ansi codes, unless --ansi (-a) switch is used
• Can accept a Nushell commandline and highlight using clip copy --nu-highlight. Uses a nu -n instance to ensure basic color codes that will work on Discord (might need to consider alternatives)
• Can accept a prefix string like # => which will be added to the beginning of each line.

cc: @Bahex for review and feedback

[Bahex]

Rendering non string input with table -e is fine, and once we're doing that including --ansi makes sense.

I feel like including nu-highlight and prefixing options are a little too much and optimizing for the specific use case of pasting to discord. I would prefer including another std command like nu-highlight-default.

PS: because $env is scoped to the command, you can just set $env.config.color_config = {} in the command and that should make table use the default colors too.

[NotTheDr01ds]

I agree with you on the nu-highlight - Probably better as a separate command. As you can probably tell, I was second-guessing this one even as I posted :-).

A prefix would be useful for any content, though. It could be a > for Markdown, a # => for doc or GitHub pasting, adding indentation, etc.

[Bahex]

I guess I can accept it. I just think of clip commands as primitive building blocks for more complex commands rather than ones to be used on their own all that much.

[NotTheDr01ds]

@Bahex You're probably right that the prefix functionality should be a separate command. I guess the only concern is that it pretty much has to duplicate the "structured-data -> string" functionality of the clip copy anyway. I've pushed an update with it separated out, though. Let me know what you think. Thanks!

[Bahex]

Looks good to me, though depending on other potential additions, we might wanna move prefix to a different module in the future, like render or format.