Open dopefishh opened 3 years ago
I'd merge patches. You might like to contribute to offlineimap3, though.
BTW, I think the best way to implement this is not to introduce yet another configuration option. I'd rather add a new "context" argument object when calling the user function.
The
postsynchook
andpresynchook
are configuration options to execute a process before of after synchronisation.In my case it would be useful to discriminate between quick syncs and full syncs in regards to post- and presynchooks. My postsynchook is quite CPU intensive and I would like to only run it on full syncs and skip it on quick syncs.
To keep it backwards compatible I propose to add four new configuration options so that there are a total of six synchooks:
presynchook
Executes before both a quick and a full syncpostsynchook
Executes after both a quick and a full syncprequicksynchook
Executes only before a quick syncpostquicksynchook
Executes only after a quick syncprefullsynchook
Executes only before a full syncpostfullsynchook
Executes only after a full syncI'm fine with implementing this but I wanted to poll enthusiasm first.