Idempotently sync changes between ikhal and orgmode about khalorg HOT 4 OPEN

The algorithm you proposed looks perfect for me. At the implementation level I feel that having a khalorg sync <calendar_name> that the user can use either on cron or systemd (with whatever it feels more comfortable with) could be an elegant solution.

I'm a little busy right now so I can't guarantee a PR in a near horizon, but it's surely something that is nagging me inside my head, so if you don't have the energy to work on it, eventually I'll do it :)

from khalorg.

Hey @lyz-code, thanks for your interest. I accept PRs.

You are correct that currently there is no "automatic sync mechanism" that handles both pulling en pushing agenda items. The solution you describe sounds logical to me.

My current workflow is that I have 1 org file holding my Outlook agenda. When I want to pull the items I run khalorg list outlook > outlook.org. When I want to push new/edited items, I use the commands from the plugin. If I forget to do this, and run the khalorg list again, I will loose information. I guess this is also the issue you are encountering.

The ideal solution, I guess, would be if:

• khal pulls the latest calendar data from the server.
• khalorg could accept 1 org file (holding all agenda items of a calendar) and negotiate with khal whether:
  • an item was changed in the org file
  • an item was changed on khal (which we updated earlier)
• based on the info above, the khal and the org file are updated.

The process above can be executed using systemd or cron using a simple timer.

I'll think about it some more this week. Let me know what you think the best approach would be.

Cheers

from khalorg.

I was just thinking. Would it not be possible to let khalorg push all its changes to khal, without checking for any sync errors, and let vdirsyncer handle the synchronization?

For example:
You have:

• remote calendar called: remote
• local calendar in khal called: local_khal
• the same local calendar as local_khal but now in org format: local_org

Lets say changes are made in remote: an existing event A is edited. At the same time, we also edit event A in org.

Now we can do the following:

• Push all changes made in local_org to local_khal using khalorg (we need to make a new command for this).
• Next we run vdirsyncer sync which will pull the changes from remote into local_khal. Here, we let vdirsyncer resolve the merge conflict in event A.
• Next, we use khalorg list to update our local_org calendar.

The process above can still be executed using timer (cron/systemd). I might be missing something here but it is a start.

from khalorg.

Makes a lot of sense to reuse vdirsyncer already in place conflict resolution. I hadn't thought of that possibility.

The workflow might be confusing for a new user though, so if we go through this path I'd definitely either:

• make the documentation cristal clear
• Create a khalorg new that asks the user the information needed to create a new calendar, and that creates the required calendars in vdirsync behind the scenes
• Create the kharlorg sync that follows the process you described (push, run vdirsyncer, list)

from khalorg.