-
Notifications
You must be signed in to change notification settings - Fork 12
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
Colour output on different terminals #20
Comments
Owl doesn't disable colours, Elixir does this by itself. Owl uses Line 266 in 5b05678
which uses IO.ANSI.enabled?/0 by default. Looks like IO.ANSI.enabled/0 returns false in prod.You can enable it manually Line 1 in 5b05678
but this keep in mind that this change is global |
I think we can add an optional second parameter to |
Thanks for the pointer, that's exactly the cause :) I have no problem enabling ansi colours for this app, so that works for now. Happy to close this issue if you are. |
Weird one here... I'm slightly abusing Owl to render an interface for a MUD that is displayed over a LiveView, and I'm hitting a funny issue when deploying.
The ansi colour codes work fine on dev, when I'm usind a LiveScreen and updating a block, I observe its
io_request
message and the colour codes are present.But when I do this in prod (Debian / Fly.io), the same messages contain no colour codes. I'm observing the raw data in logs:
dev
prod
(No colour codes)
Any pointers for what might be happening? I've been trying to debug this morning and my best guess is that Owl is doing some kind of terminal support check and disabling colours...
The text was updated successfully, but these errors were encountered: