From: David Masterson <email@example.com>
To: Neil Jerram <firstname.lastname@example.org>
Cc: Org Mode List <email@example.com>
Subject: Re: Org-GCal ?
Date: Mon, 30 Nov 2020 13:19:50 -0800 [thread overview]
Message-ID: <SJ0PR03MB5455BF4EC2EA9542AFA3A5959BF50@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <CAKuG=vuUyR1Qi2R-uwM_Nvz0pPguwjBJAmexZ5v+Bvgz0BxHPg@mail.gmail.com> (Neil Jerram's message of "Mon, 30 Nov 2020 10:02:36 +0000")
Neil Jerram <firstname.lastname@example.org> writes:
> On Mon, 30 Nov 2020 at 00:49, David Masterson <email@example.com> wrote:
> Anyone using org-gcal? I just got it hooked up and am now trying to
> figure out how to fit it into my workflow. 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).
> That was my observation too: it generates and maintains one .org file per Google calendar.
> How does that create a problem for you?
My workflow has a number of Org files (one per ~project) with
tasks/events related to the project in the associated Org file. Agenda
can pull all the tasks together, so it seemed a natural workflow. I
wasn't thinking of creating a calendar per project as they are not
worthy of that -- one calendar would do to share my events with the
next prev parent reply other threads:[~2020-11-30 21:20 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 [this message]
2020-12-01 11:58 ` Neil Jerram
2020-11-30 11:19 ` Peter Hardy
2020-11-30 21:21 ` David Masterson
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 \
* 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).