Re: Saving data after each action

[Ulrik Sverdrup <ulrik sverdrup gmail com>]

2011/2/23 SanskritFritz <sanskritfritz gmail com>:
> Thanks Karol, this looks great, tested already, haven't found any issues.
> I'm going to use this patched version from now on, and report back on any
> issues.

Hi there,

I'll just mention this first -- kupfer exits gracefully as long as
it's not forcibly killed (X dies), so sending the TERM signal is
enough at logoff (killall kupfer) and you will be fine! Or if you
prefer this dbus method:

dbus-send --type=method_call --print-reply --dest=se.kaizer.kupfer
/interface se.kaizer.kupfer.Listener.Quit

(I'll try to add kupfer --quit as a shorter way to send that)

I've been away from Kupfer for some time and I'm looking at it now --
there are lots of bugs and suggestions reported. Saving data
periodically is good I think, but I'd prefer to save only data and
skip the ugly caching method (Triggers and Favorites use the data
method and the clipboard uses only the caching method, since we judged
clipboards are not important data. That should probably change).

(Also, Kupfer loses caches often at version upgrades and willingly so.
But for the data files our aim is that users never lose that data. So
far we haven't had any data format changes there I think..)

Ulrik