Lemonboy's bar doesn't accept a string too long, or it doesn't print the entire thing. For one instance per screen, it's not really an issue, but it is for a unique lemonbar instance with a multiple screen setup.
I can't change directly this behaviour, but maybe the panel can "clean" each string sent to the bar, to clean redundancies. It would be specially useful with the fg and bg definitions, as barython doesn't really try to avoid duplicates for now, it just ensures that the defined colours will be applied.
This solution will not be magical, though, as if there as still too much info after a clean, lemonbar will have the same behaviour than now.
In all cases, you might switch to a per-screen instance if you have more than 1 screen.
Lemonboy's bar doesn't accept a string too long, or it doesn't print the entire thing. For one instance per screen, it's not really an issue, but it is for a unique lemonbar instance with a multiple screen setup.
I can't change directly this behaviour, but maybe the panel can "clean" each string sent to the bar, to clean redundancies. It would be specially useful with the fg and bg definitions, as barython doesn't really try to avoid duplicates for now, it just ensures that the defined colours will be applied. This solution will not be magical, though, as if there as still too much info after a clean, lemonbar will have the same behaviour than now.
In all cases, you might switch to a per-screen instance if you have more than 1 screen.