Workaround conky/issues/1479 #2238
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lasers
reviewed
Feb 29, 2024
Co-authored-by: lasers <lasers@users.noreply.github.com>
lasers
approved these changes
Mar 1, 2024
|
Thank you for your first contribution @ntorresalberto ! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
The conky module seems to be broken for some time now.
I took a look at it and it seems some time in 2022 conky devs introduced a change in the text output when
out_to_x=falsethat is used by the conky module, as mentioned in brndnmtthws/conky#1479.This means that there's an unexpected line in the process output that's breaking the formatting.