From: Niels Giesen <niels.giesen@gmail.com>
To: Stephen Eglen <S.J.Eglen@damtp.cam.ac.uk>
Cc: emacs-orgmode@gnu.org
Subject: Re: Status google calendar sync
Date: Sat, 11 Jun 2011 19:32:58 +0200 [thread overview]
Message-ID: <BANLkTi=f9dHCzZbJt0AW0n3PVh+b5bf7uA@mail.gmail.com> (raw)
In-Reply-To: <t5xsjrhfsci.fsf@rgc.damtp.cam.ac.uk>
> When going from org -> google, do I need to do anything about using
> org-icalendar-store-UID? I'd rather not have to populate my org files
> with :ID: entries.
You do not strictly need to, but this is the only way you do not
create double events when exporting an org file to .ics and importing
it into google calendar. If you do use them, a change in a date in
org-mode will be reflected as such in google calendar.
Note that if you /do/ want to store uids for the reason I just wrote,
/and/ if you use diary sexps, you'll need an up-to-date Emacs (from
bazaar) and below patch to org-icalendar.el (this has not been applied
yet to org-mode, alas). Otherwise icalendar.el creates a new uid every
time you export anyway.
--- a/lisp/org-icalendar.el
+++ b/lisp/org-icalendar.el
@@ -412,7 +412,10 @@ When COMBINE is non nil, add the category to each line."
(if scheduledp (setq summary (concat "S: " summary)))
(if (string-match "\\`<%%" ts)
(with-current-buffer sexp-buffer
- (insert (substring ts 1 -1) " " summary "\n"))
+ (let ((entry (substring ts 1 -1)))
+ (put-text-property 0 1 'uid
+ (concat " " prefix uid) entry)
+ (insert entry " " summary "\n")))
(princ (format "BEGIN:VEVENT
UID: %s
%s
--
http://pft.github.com
next prev parent reply other threads:[~2011-06-11 17:33 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 0:54 Status google calendar sync Torsten Wagner
2011-02-01 9:12 ` Eric S Fraga
2011-02-01 22:44 ` Sven Bretfeld
2011-02-02 5:15 ` Torsten Wagner
2011-02-02 8:30 ` Konrad Hinsen
2011-02-14 21:39 ` Marcelo de Moraes Serpa
2011-02-15 7:18 ` Konrad Hinsen
2011-02-15 16:37 ` Marcelo de Moraes Serpa
2011-02-15 16:43 ` Marcelo de Moraes Serpa
2011-02-15 16:55 ` Bastien
2011-06-10 16:58 ` Stephen Eglen
2011-06-10 17:04 ` Arun Persaud
2011-06-10 18:34 ` Stephen Eglen
2011-06-10 19:09 ` Arun Persaud
2011-06-11 13:25 ` Philipp Haselwarter
2011-06-11 18:38 ` Nick Dokos
2011-06-15 19:00 ` Eric S Fraga
2011-06-11 17:32 ` Niels Giesen [this message]
2011-06-30 16:14 ` Bastien
2011-06-15 18:45 ` Eric S Fraga
[not found] ` <87hb7rory9.fsf@ucl.ac.uk>
2011-06-16 12:13 ` Stephen Eglen
-- strict thread matches above, loose matches on Subject: below --
2011-01-29 14:53 Torsten Wagner
2011-01-29 19:38 ` Mark Elston
2011-01-29 20:44 ` Greg Troxel
2011-01-30 4:36 ` Mark Elston
2011-01-30 13:28 ` Greg Troxel
2011-01-30 14:09 ` Eric S Fraga
2011-01-30 20:43 ` Arun Persaud
2011-01-30 21:36 ` Mark Elston
2011-01-30 14:01 ` Eric S Fraga
2011-01-30 1:21 ` Eric S Fraga
2011-01-31 10:02 ` Christopher Witte
2011-02-01 9:07 ` Eric S Fraga
2011-01-21 8:38 Torsten Wagner
2011-01-21 9:43 ` Ian Barton
2011-01-21 15:22 ` Nick Dokos
2011-01-21 18:19 ` Arun Persaud
2011-01-21 23:58 ` Eric S Fraga
2011-01-25 20:21 ` Arun Persaud
2011-01-26 12:33 ` Eric S Fraga
2011-01-26 23:29 ` Mark Elston
2011-01-27 0:52 ` Arun Persaud
2011-01-27 2:51 ` Mark Elston
2011-01-27 19:43 ` Arun Persaud
2011-01-27 21:57 ` Arun Persaud
2011-01-28 16:13 ` Eric S Fraga
2011-01-31 19:03 ` Bastien
2011-01-29 1:28 ` Greg Troxel
2011-01-29 12:45 ` Eric S Fraga
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='BANLkTi=f9dHCzZbJt0AW0n3PVh+b5bf7uA@mail.gmail.com' \
--to=niels.giesen@gmail.com \
--cc=S.J.Eglen@damtp.cam.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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).