Travelling through several timezones, I found that redshift neither
updates its understanding of what nighttime is (based on the
timezone), nor does it make any efforts to re-acquire its position.
Maybe it could instead listen to appropriate events, or just reset
itself every hour or so.

Hello Martin,

What desktop framework are you using ? And how exactly are you using
redshift ?

The current redshift now has support for geoclue2, which should give it
the information initially. But, like you have reported, I need to check
on how it behaves/honors changes in those events.

also sprach Ritesh Raj Sarraf <rrs@researchut.com> [2015-12-21 20:37 +1300]:

None.

I run redshift-gtk from .xsession.

Thank you!

I'm thinking how this should be done. redshift (cli) can acquire
location from geoclue2. But that's it.

In the past, all desktop plugins did these tasks. For example, the
previous KDE based plugin took care of changing redshift settings based
on which plasma activity you are in.

Ideally, a desktop plugin should do this. It should be able to acquire
a bus on the desktop bus, read data from geoclue2, and then accordingly
re-instate redshift.

I think the KDE ones used to do it. The GNOME plugin, gnome-shell-
extension-redshift, doesn't do it.

Should redshift-gtk do it ? I don't know. Because it'd have to
integrate with dbus and the desktop frameworks, for which there are
other plugins already.

You may want to file this bug report upstream ?
But given the development on the GUI, I doubt much would change.

https://github.com/jonls/redshift

Let's not overcomplicate things. All that redshift needs to do is
regularly obtain the current timezone from the system, and get an
updated position from the location provider. Shouldn't be that hard
to do, and would beat regularly killing and restarting.