emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Masterson <dsmasterson92630@outlook.com>
To: Peter Hardy <peter@hardy.dropbear.id.au>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org-GCal ?
Date: Mon, 30 Nov 2020 13:21:07 -0800	[thread overview]
Message-ID: <SJ0PR03MB5455B5AEB078C1898B0C763F9BF50@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <m2a6uz5byw.fsf@graphite.lan> (Peter Hardy's message of "Mon, 30 Nov 2020 22:19:03 +1100")

Peter Hardy <peter@hardy.dropbear.id.au> writes:

> David Masterson writes:
>> My issue is (CMIAW) that
>> org-gcal seems to have a 1 to 1 connection between a Google calendar and
>> an Org file (org-gcal-file-alist).  I'm trying to figure out how to use
>> this when my workflow is split across many Org files.
> Have you considered using org-caldav instead? It can sync across several
> org files - events created in org can live in any of them, while events
> created in gcal will be synced to an inbox file, and can be easily
> moved.
> I haven't personally tried it syncing with gcal, but it claims to
> work. And a superficial read of both org-gcal and org-caldav READMEs
> suggest they use the same authentication workflow.
> https://github.com/dengste/org-caldav

I'm keeping an eye on that, but I haven't figured it out yet.

David Masterson

      reply	other threads:[~2020-11-30 21:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30  0:32 Org-GCal ? David Masterson
2020-11-30 10:02 ` Neil Jerram
2020-11-30 21:19   ` David Masterson
2020-12-01 11:58     ` Neil Jerram
2020-11-30 11:19 ` Peter Hardy
2020-11-30 21:21   ` David Masterson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=SJ0PR03MB5455B5AEB078C1898B0C763F9BF50@SJ0PR03MB5455.namprd03.prod.outlook.com \
    --to=dsmasterson92630@outlook.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=peter@hardy.dropbear.id.au \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).