From: knubee <knubee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: calendar/diary <-> phone?
Date: Fri, 25 Jan 2008 21:08:14 -0800 (PST) [thread overview]
Message-ID: <c986b34a-f5b4-47cc-94bf-dc3a5bf33d3e@i29g2000prf.googlegroups.com> (raw)
In-Reply-To: mailman.5379.1198587287.18990.help-gnu-emacs@gnu.org
> I use Gnokii along with the attached elisp hack.
thanks for the reply.
i have since learned that the most common way to synchronize is to
convert the file to icalendar (.ics) format. then there are various
ways that phones can sync with that file. in case this will be useful
to others, details below -- as well as a couple of problems i have
encountered with icalendar.el
if i understand correctly, the sync model is something like this:
emacs <-> .ics file <-> phone
there seem to be several strategies for getting the .ics file to sync
with phone (using, e.g, bluetooth)
- use a specific app that phone understands
- have an "intermediary" app read the .ics file (evolution,
lightening/sunbird, google calendar, etc.) -- and then sync between
phone and the calendar in that app (which has its own mechanisms for
syncing with phone).
note that if one wants to go the google calendar route, it is worth
looking at Bill Clementson's blog post on "Emacs and Google
Calendars" - http://bc.tech.coop/blog/070306.html
also: gcal.el (part of emacspeak, but possible to use separately as
part of the "g-client" emacs package for google services) -
http://code.google.com/p/emacspeak/
also; gcaldaemon - http://gcaldaemon.sourceforge.net/
- install a syncing "framework" on computer (e.g., opensync ... which
works, but is still a bit rough around the edges)
the main problem i have is the difficulty of getting recurring events
from emacs diary file into an .ics file.
for example, icalendar.el (version 0.15 included in emacs22) does not
fully handle sexps and recurring events. for my purposes, the main
limitation is that icalendar.el does not correctly export recurring
weekly/monthly events -- namely, these simply do not appear in the
resulting .ics file.
; weekly or monthly entries to not appear in .ics file
Saturday take a nap
28 * shoot the moon
(Note: however, yearly events do appear correctly in resulting .ics
file.)
25 December Some guy's birthday
RRULE:FREQ=YEARLY;INTERVAL=1;BYMONTH=12;BYMONTHDAY=25
; sexp recurring events do not appear in .ics file
%%(and (= (calendar-day-of-week date) 1)
(diary-block 13 1 2008 13 5 2008)) 14:00-16:00 Do something
each week for 4 months
Recurring events are crucial so it would be nice if there was a way to
get them from emacs diary file into .ics format. Does anyone know a
solution to this? Is there a newer version of icalendar.el that works?
Are there alternatives to icalender.el that work? Or?
thanks
prev parent reply other threads:[~2008-01-26 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-19 15:19 calendar/diary <-> phone? knubee
2007-12-25 12:50 ` Magnus Henoch
[not found] ` <mailman.5379.1198587287.18990.help-gnu-emacs@gnu.org>
2008-01-26 5:08 ` knubee [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c986b34a-f5b4-47cc-94bf-dc3a5bf33d3e@i29g2000prf.googlegroups.com \
--to=knubee@gmail.com \
--cc=help-gnu-emacs@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.
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).