Paul Eggert via tz wrote in
<[email protected]>:
|I installed the attached proposed patch, which adds a tzcode option to
|periodically poll the TZif file to see whether it changed. You can
What a terrible thing, isn't it. It is optional as you say.
You know, if it would be a possibility to install a handler,
so that all the many programs which actually run an eventloop
can simply integrate the one in likely the set of the not-few
paths that are monitored (often, at least; like resolv.conf,
hosts, and what do i know on the many XDG config places that
possibly even exist, mailcap etcetc). Like eg tz_hook(enum
act{install,uninstall,trigger}, (*hook)(?), char const * const *
path_(to_)watch(ed)), or something. And use the poll code if no
hook is set?
|enable this option by compiling with -DTZ_CHANGE_INTERVAL=61 (or choose
|your own favorite polling interval instead of 61 seconds). The option
|affects localtime and other functions whose behavior depends on the TZ
|environment variable (or its absence); it does not affect
|tzalloc-related functions.
|
|This patch affects tzcode's behavior only if you compile with the new
|option.
...
I mean, i such poll monitors myself, but it can be wrong for
X seconds, and what sense does this make, then?
And i would assume many frameworks have a central notification
mechanism .. i recall having used for example KDE around maybe
2001/2 at early stages, and it was quite thrilling to change the
language aka locale and see that (slow) event wave in the UI.
Isn't it horror to have buried so-and-so many such poll notifiers
in buried library paths. And what if i do not care at all.
A nice Sunday from Germany i wish,
--steffen
|
|Der Kragenbaer, The moon bear,
|der holt sich munter he cheerfully and one by one
|einen nach dem anderen runter wa.ks himself off
|(By Robert Gernhardt)
