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
Publish 2.0.0 to NPM #39
Comments
So I just noticed that the latest version (2.0.0) actually already does this! But it's not published to NPM... :( So I'm changing my issue to be a request to publish the latest version to NPM. Thanks! |
doughsay
changed the title
True-color and 256 color should (optionally) inline styles
Publish 2.0.0 to NPM
Jun 13, 2017
Hi doughsay - I will get this pushed next week. Thank you. |
Thanks!
…On Thu, Jun 15, 2017, 3:59 PM Dru Nelson ***@***.***> wrote:
Hi doughsay - I will get this pushed next week. Thank you.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#39 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AANh_dRVCkuu6apP2xLUDmvP2t0vNJsIks5sEbdGgaJpZM4N43YO>
.
|
Ok - npm pushed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The 16 basic ansi colors can be open to interpretation, many themes exist out there defining what the colors look like, so having the
use_classes
option is great for that.But the 256 color palette and true-color aren't really open for interpretation, they are exact color specifications. I was wondering if we could add an option to allow for using classes for the basic 16 colors, but when rendering 256 or true-color, use inline styles.
Right now, if you
use_classes
and render 256 color, it renders a class, which could theoretically be used to build a stylesheet for all 256 colors (but that would be tedious). But for true-color, it only adds adata-
attribute, which would mean I'd need to add an extra js library of some sort to actually apply the color. Seems like ansi_up could do that for me instead, right?The text was updated successfully, but these errors were encountered: