Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Proposal] - Adding a mox/moccassin banner + color the output of default man help screen #221

Open
xyizko opened this issue Feb 28, 2025 · 3 comments

Comments

@xyizko
Copy link

xyizko commented Feb 28, 2025

Rationale

  1. Sometimes when running multiple utilities in scripts a banner makes it visually easier to examine specific tool;s execution for enhancing debugging. Eg: Banner of CyfrinUP , Soldeer , both of which I had added.

  2. Adding some color to the default help text of the arguments. It would like the color usage if he default UV output eg:

Illustration

Screen Shot UV default text

Image

Design

Banner

  1. Primary Color Orange ( of the moccassin banner )
  2. Would be the M logo in ascii , generated with online or local tooling

Adding Color to default text

  1. Primary Color Orange of the left hand text ( of the moccassin banner)

How ?

  1. Using rich
  2. Using minimally invasive code without significant alternation of the code structure
  3. Rich is quite powerful , and perhaps other error messages and confirmatory messages could have this implementation also

To be clear this proposal is not a request , what I mean was , i would implement it if it fits the maintainers criteria

@s3bc40
Copy link
Contributor

s3bc40 commented Feb 28, 2025

I didn't know that it could be great, I'll take a look later. @PatrickAlphaC it could be good to check

@PatrickAlphaC
Copy link
Member

Love this idea.

My concern -> performance.

So long as it doesn't impact the benchmarks I'd love this.

@xyizko
Copy link
Author

xyizko commented Mar 7, 2025

  1. Yes , i understand adding a new library can introduce overheads. I will run the tests with more realistic specs, most probably on a Debian 16GB VM
  2. Anyway as I run my investigations I will post findings HERE for decision making..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants