On Wed, Oct 8, 2014 at 11:23 AM, Markus Teich
<markus.teich_AT_stusta.mhn.de> wrote:
> Now the first problem occured when I was travelling to another timezone and
> updated my timezone information. Since clock only get's initialized once, we
> don't catch the new timezone info and the displayed time stays in the old
> timezone until the script is restarted.
As a non-serious contribution to this discussion, I'd recommend
watching the 4:12–5:40 part of "Liberating the Smalltalk lurking in C
and Unix" talk[0]. Synopsis: you can *dynamically* change the timezone
of an xclock instance by (1) attaching it to gdb and (2) tempering
with the environment variable directly.
[0]
https://www.youtube.com/watch?v=LwicN2u6Dro
Cheers,
--
______________
Raphaël Proust
Received on Wed Oct 08 2014 - 14:34:47 CEST