Closed chenspc closed 3 years ago
haha, this is because Pluto doesn't support ASCII color characters - would be nice if Pluto supports it. I'm not sure what's the right way to disable it, it's probably a question for Pluto.
@fonsp I'm wondering if there is a way to let the default HTML printing fallback to Pluto?
I guess we can assume that Configurations.jl would replace the previous option types defined manually inside Pluto, so some special handling based on is_option
method is possible.
I think I'd just want the printing of option types defined by Configurations to be the same as how Pluto visualize normal Julia types, but it seems Pluto will not use the builtin method if Base.show
is overloaded.
I'll look into this!
@fonsp I found a solution to this: https://juliadocs.github.io/ANSIColoredPrinters.jl/dev/
this allows me to replace the ASCII color escape characters with HTML class, but then I will need to use some CSS to visualize it for Pluto. Wondering what would be the best HTML output for Pluto?
or should I use a different MIME type other than text/html
current since Pluto doesn't have a CSS definition of ASCII types, you would get the following with this method
but I still prefer the default Pluto visualization...
I was trying to using
Configurations.jl
inPluto.jl
. When making an option type object, the printing shows extract characters. Not sure if this is an issue more suitable here or inPluto.jl
..