Open BETLOG opened 1 year ago
Happens because variables are evaluated before text content is built.
Fixing it requires handling obj->callbacks.iftest
in extract_variable_text_internal
similarly to how it's handled in generate_text_internal.
dumb bot...
What happened?
I have written a single conky.conf to use on 3 different machines, two of which do not have a GPU, using
${if_match "${nodename}"=="betlognuc"}
to prevent the relevant machines from trying to parse commands they cannot execute.However they do anyway. Resulting in a slew of error messages.
I understand that conky parses the entire config, but surely it can be a little smarter about it.
Version
conky 1.18.0 compiled 2023-02-20 for Linux x86_64
Which OS/distro are you seeing the problem on?
Ubuntu
Conky config
Stack trace
No response
Relevant log output