From: Eric S Fraga <esflists@gmail.com>
To: Matt Price <moptop99@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: ics calendar?
Date: Thu, 07 Sep 2017 17:00:35 +0100 [thread overview]
Message-ID: <87pob2mrbw.fsf@t3610> (raw)
In-Reply-To: <CAN_Dec8fdUN7vEBdEVUjC4VuhkYq2+xsSrOY8nYFB=tSHsJjRw@mail.gmail.com> (Matt Price's message of "Thu, 7 Sep 2017 10:18:16 -0400")
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
On Thursday, 7 Sep 2017 at 10:18, Matt Price wrote:
> So I'm really just asking whether other people do ics exports and if
> so, how you structure the org source files and so forth.
I use ics export to make my calendar available to my phone. I have a
script that I run periodically which has the following lines:
--8<---------------cut here---------------start------------->8---
DIARY=...where my diary.org file resides...
emacs -Q --batch --debug-init \
--directory=${HOME}/s/emacs \
--load=custom.el \
--load=esf-org.el --visit=${DIARY}.org --eval='(org-icalendar-export-to-ics)'
--8<---------------cut here---------------end--------------->8---
and I then copy the resulting ics file to where Google Calendar, for
instance, can find it. My custom.el has all of my Emacs customizations
and esf-org.el my org specific customizations.
I export all of my appointments and nothing else. Tasks etc. are in
other org files. I simply want my Pebble watch to vibrate when I have
an upcoming appointment and that's connected to my phone which needs my
calendar etc. etc. etc. :-) Sounds like the "For the want of a nail, the
kingdom was lost" kind of story: from Emacs via org to my watch in N
easy steps!
HTH,
eric
--
: Eric S Fraga via Emacs 26.0.50, Org release_9.0.10-723-g23eba9
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2017-09-07 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 14:18 ics calendar? Matt Price
2017-09-07 16:00 ` Eric S Fraga [this message]
2017-09-08 9:13 ` Rasmus
2017-09-08 15:52 ` Eric Abrahamsen
2017-09-11 13:45 ` Matt Price
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87pob2mrbw.fsf@t3610 \
--to=esflists@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=moptop99@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).