forked from myuhe/org-gcal.el
-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to mark events as managed by org-gcal for purposes of org-gcal-sync #127
Labels
enhancement
New feature or request
Comments
telotortium
added a commit
to telotortium/org-gcal.el
that referenced
this issue
Feb 27, 2021
1 task
telotortium
added a commit
to telotortium/org-gcal.el
that referenced
this issue
Feb 27, 2021
telotortium
added a commit
to telotortium/org-gcal.el
that referenced
this issue
Mar 3, 2021
telotortium
added a commit
to telotortium/org-gcal.el
that referenced
this issue
Mar 3, 2021
telotortium
added a commit
to telotortium/org-gcal.el
that referenced
this issue
Mar 4, 2021
telotortium
added a commit
to telotortium/org-gcal.el
that referenced
this issue
Mar 13, 2021
telotortium
added a commit
to telotortium/org-gcal.el
that referenced
this issue
Apr 6, 2021
telotortium
added a commit
to telotortium/org-gcal.el
that referenced
this issue
Apr 6, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Overview
Currently, I mainly use
org-gcal-fetch
, notorg-gcal-sync
, to avoid accidentally modifying shared events that I've fetched. I'd like to be able to useorg-gcal-sync
to be able to manage events associated with Org mode headlines that I manage in Org mode - clocking time, changing title, description, schedule, etc. Currently I runorg-gcal-fetch
, and when I want to push changes from a headline in Org mode to the event in Google Calendar, I manually runorg-gcal-post-at-point
. This is cumbersome if you manage a lot of events in Org mode files and are subscribed to a lot of shared calendars as well.I'm envisioning adding a property
org-gcal-managed
to all events withcalendar-id
andentry-id
properties. This property will have two values:org
: Event is intended to be managed primarily byorg-gcal
. These events will be pushed to Google Calendar byorg-gcal-sync
,org-gcal-sync-buffer
, andorg-gcal-post-at-point
if they have been modified in the Org file. If the ETag is out of sync with Google Calendar, the Org headline will still be updated from Google Calendar.gcal
: Event is intended to be managed primarily byorg-gcal
. These events will not be pushed to Google Calendar by bulk update functions likeorg-gcal-sync
,org-gcal-sync-buffer
. When runningorg-gcal-post-at-point
, the user will be prompted to approve pushing the event by default.The intended end state is that when
org-gcal-sync
andorg-gcal-sync-buffer
are run, it will operate like the sync functions operate today on events whereorg-gcal-managed
is set toorg
, but will operate likeorg-gcal-fetch
andorg-gcal-fetch-buffer
do on events whereorg-gcal-managed
is set togcal
.How is the
org-gcal-managed
property set on events without the property?I'll create separate
defcustom
to override the default property values for each of these cases:org-gcal-sync
ororg-gcal-fetch
:gcal
.org-gcal-managed
property is updated:gcal
.org-gcal-post-at-point
(i.e.,calendar-id
andentry-id
properties are added to an event previously without them):org
.Updating from previous versions
The above defaults will preserve the previous behavior for previously-downloaded events - all such events will default to
gcal
. If a user wants to manually setorg-gcal-managed
to a preferred value, I will document how to programmatically set the property on all events in a buffer.The text was updated successfully, but these errors were encountered: