-
Notifications
You must be signed in to change notification settings - Fork 31
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
Wrong escapes, am I doing something wrong? #41
Comments
@gillchristian Glad this library was helpful for you. Can you share what the HTML generated from the component looks like? It might be the case that the color key codes are not properly mapped to classnames for styling. |
Using the inline styles mode instead of the classes one. I guess it should not change the parsing, right? <code>
<span>$ docker-compose down</span>
</code>
<code>
<span>Stopping server_tsplay_1 ... </span>
</code>
<code>
<span>Removing server_tsplay_1 ... mdone</span>
<span> </span>
</code>
<code>
<span>Removing network server_defaultone</span>
</code>
<code>
<span>$ docker-compose up -d</span>
</code>
<code>
<span>Creating network "server_default" with the default driver</span>
</code
<code>
<span>Creating server_tsplay_1 ... </span>
</code>
<code>
<span>$ docker-compose logs... </span>
<span style="color: rgb(0, 187, 0);">done</span>
</code>
<code>
<span>Attaching to server_tsplay_1</span>
</code> |
OK. I looked into this. I'm not sure why that lonesome "done" renders with the correct color codes but when I tried to repro this nothing was colorizing for me. I noticed in the input text that the color codes are not prefixed with |
Hi! This is a really cool library, it made the problem of the rendering of ANSI for a project I work just stupidly easy 😅 Thanks!
I found a problem with some stuff that is not properly rendered and I'm not sure if I'm doing something wrong (with the input) or if it is a bug.
I have the following text:
This is how it looks on the terminal:
And this is how it looks rendered (split by line):
This is just the text, just in case it serves as reference.
The text was updated successfully, but these errors were encountered: