Control: forwarded -1 https://github.com/brndnmtthws/conky/issues/62
Hi Francesco, On Tue, Jul 7, 2015 at 1:28 PM, Francesco Poli (wintermute) <invernom...@paranoici.org> wrote: > Package: conky-std > Version: 1.10.0-1 > Severity: normal > > Hello Vincent, > I've recently upgraded conky on my Debian testing boxes: > [UPGRADE] conky-std:amd64 1.9.0-6 -> 1.10.0-1 > > I noticed that the pre_exec variable has been removed, without > providing anything with an equivalent behavior. > This seems to be confirmed by: > https://github.com/brndnmtthws/conky/issues/62 > https://github.com/brndnmtthws/conky/commit/b96f112106ea43dda5b5747bc315a2b76ba9da8f > > The commit description says that the pre_exec variable has been removed > "because one can use lua to generate the config on the startup, if one > wants to". > > Oh well, if one *knew* how to program in Lua, one could use Lua > to generate the config on startup! > I have currently no knowledge about Lua, so I am a bit lost without > some example in the documentation. > > I failed to find any relevant explanation on how Lua could be used > to emulate the behavior of pre_exec... > > My attempt (after converting my .conkyrc to the new Lua-based syntax) > is the following: > > $ cat .config/conky/conky.conf > -- vim: syntax=lua > > conky.config = { > -- many settings... > lua_startup_hook = 'conky_cow', -- append fortune said by a cow > }; > > -- stuff to be formatted on screen > conky.text = [[ > a lot of stuff... > ${color green} > ]]; > > function conky_cow() > o = io.popen('fortune -s | cowsay', 'r') > conky.text = conky.text .. o:read('*a') > end > > > Unfortunately, it does not work and I do not know why. > In case you happen to know how I can emulate pre_exec, please > help me, and/or forward my bug report upstream. Unfortunately I can't help you much with this either; I myself am unfamiliar with conky's new lua configuration (and there's very little documentation upstream about it), and I don't know of a way to emulate/replace pre_exec functionality with 1.10. I'll forward your message to that upstream bug report, but that's about all I can do to help, sorry! Regards, Vincent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
