Conky: Double monitor - different sizes - gap_y incorrectly
Hi,
I have two monitors, one in vertical with height of 1280, one normal with height of 1024.
When I set conky to show in that monitor, gap_x works as expected, gap_y no.
It seems that gap_y takes care of the first one monitor (height 1024).. so the result is more padding than expected.
Here I set gap_y = 20
The problem does not occur only if I run conky from a terminal that's placed in the 1024h.
If move terminal on the vertical one 1280h (where gap_x refers to), everything is right.
LeoIannacone
All 3 comments
I'm going to link this issue up with #173, since it appears to be related.
marcpayne
on 29 Nov 2015
3 years 2 months passed. Can you determine if you're still having this problem today on 1.10.8 or 1.10.9_pre? The older versions are not trustworthy. Thank you. Possibly resolved by #173's PR.
lasers
on 6 Aug 2018
Hi friends. To start things off, this issue is with an old pre.1.10 config.
I tested this issue with (new) default config on the following layouts:
The new default config contains 50+ settings. The important settings are alignment = 'top_left', gap_x = 5, and gap_y = 60. I added xinerama_head on top of this config with either 0 or 1.
Everything looks fine on my end.
The linked PR above appears to be related and was merged in Dec 4, 2015. That's when this issue could had been closed... roughly 5 months 16 days later. Since that didn't happen, I will be closing this issue now instead... roughly 3 years 3 months later. Cheers! :blush:
lasers
on 30 Aug 2018
Related issues
ghost
·
4Comments
zero77
·
3Comments
Dimerbone
·
4Comments
Microcrap
·
4Comments
sdban
·
4Comments
Most helpful comment
Hi friends. To start things off, this issue is with an old pre.1.10 config.
I tested this issue with (new) default config on the following layouts:
The new default config contains 50+ settings. The important settings are
alignment = 'top_left',gap_x = 5, andgap_y = 60. I addedxinerama_headon top of this config with either0or1.Everything looks fine on my end.
The linked PR above appears to be related and was merged in Dec 4, 2015. That's when this issue could had been closed... roughly 5 months 16 days later. Since that didn't happen, I will be closing this issue now instead... roughly 3 years 3 months later. Cheers! :blush: