I have this piece of code which is supposed to display my hometown's weather:
${texeci 100 curl -s wttr.in | sed -n '3,7{s/\d27\[0-9;]*m//g;s/^..//;s/ *$//;p}'}
Instead of showing it like here, it appears like this:

I tried changing the font, but they all produce the same output. What gives?
Hi! These characters are escape-sequences that are used to set text / background colour in a terminal. Conky doesn't know how to interpret them and only sees them as characters.
I havent tried it but something like this may help
Interesting, but how do I use it?
Although this script converts escape-sequences to conky-understandable variables such as color1, color2, etc, conky doesn't understand the output as its own-script thus can't replace them with actual colors.
You can see this if you put the ansi2conky script in the same directory as your conky-config and use this code instead:
${texeci 100 curl -s wttr.in | sed -n '3,7{s/\d27\[0-9;]*m//g;s/^..//;s/ *$//;p}' | ./ansi2conky}
I think this command fixes it:
${eval ${execi 100 curl -s wttr.in | sed -n '3,7{s/\d27\[0-9;]*m//g;s/^..//;s/ *$//;p}' | ./ansi2conky}}
By using an ${eval ...} variable whatever output comes from our code above must be processed by CONKY.
Conky will see all the ${colorX} variables and will replace them with colors appropriately.
Right now I'm fighting with the fact that my .conky can't see the script right next to it... says it's not found... chmod +x, right?
Yeah that could be a reason
So close!

Is it a font issue now?
Also, i'm only using FFFFFF, it's an all white Conky...
No. The escape-sequences on the left can be eliminated (I suppose) by patching more the ansi2conky script.
But that needs knowledge of reg-expressions which I don't have. Probably someone else may be able to help you from here 鈽猴笍
For the color, it is up to you to set it using the color0 etc variables.
NOTE: There could also be a script out there that does escape-sequences to conky convertion
${execpi 100 curl -s wttr.in | sed -n '3,7{s/\d27\[0-9;]*m//g;s/^..//;s/ *$//;p}' | ./ansi2conky}
This should have the same effect with the previous code but it is now cleaner. Not sure which is more resource consuming though.
NOTE: I am testing the code on a port of conky for macOS, and sed is not the same here.
As a result I accidentally gave you code that uses gsed.
I updated the code and now it is correct, though it seems that it worked for you anyway.
Resources are not a problem for me, I just need a working Conky. Thank you so much for your help, hope someone else here can also chip in with some ideas...
Also, the last line of code you've sent me now displays all the info and the complete ASCII art, now it all just needs to remove the escape sequences on the beginning of every line.
Thats awesome!