This behavior only happens in my Dell Inspiron (AMD Radeon), not in my Asus computer, both using Arch. Cutting to the cheese:
Here is what I get after running Pywal on an image (wal -i image.png):
Closing the terminal and opening it again results in this:
Somehow pywal sends incorrect colors to active terminals. But everything is corrected when opening new ones. That's really odd...
What do you think it could be?
I know it is in the sending part (wal.sequences.send) because the cached files make sense (colors 0 and 7, as well as foreground and background, make sense: each element of these pairs are different from the other). Also, I made a little script like the one in the documentation and saw that colors are managed fine through the code. But when the wal.sequences.send line is NOT commented, the current terminal colors become odd.
This behavior only happens in my Dell Inspiron (AMD Radeon), not in my Asus computer, both using Arch. Cutting to the cheese:
Here is what I get after running Pywal on an image (
wal -i image.png):Closing the terminal and opening it again results in this:
Somehow pywal sends incorrect colors to active terminals. But everything is corrected when opening new ones. That's really odd... What do you think it could be?
I know it is in the sending part (wal.sequences.send) because the cached files make sense (colors 0 and 7, as well as foreground and background, make sense: each element of these pairs are different from the other). Also, I made a little script like the one in the documentation and saw that colors are managed fine through the code. But when the wal.sequences.send line is NOT commented, the current terminal colors become odd.
Thank you beforehand!