emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sven Bretfeld" <sven.bretfeld@gmx.ch>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: emacs-org <emacs-orgmode@gnu.org>
Subject: Re: Adding entries to Google calendar
Date: 8 Sep 2010 11:04:15 +0200	[thread overview]
Message-ID: <87pqwosj1s.fsf@rub.de> (raw)
In-Reply-To: <87pqwsxvg3.wl%ucecesf@ucl.ac.uk> (Eric S. Fraga's message of "Sun, 05 Sep 2010 12:48:28 +0100")

Hi Eric

Eric S Fraga <ucecesf@ucl.ac.uk> writes:

>> Alas, there seems no description of the possible syntactical variants
>> available on the web. 
>
> Yes, Google do not appear to be very forthcoming with their parsing
> algorithms.  I had to do a lot of trial and error, especially to
> support block entries, and I think the result is fragile at best.

So far it works with the language of GoogleCalendar set to US English.

>>   2. We have to isolate the time of day from the diary-entry as a
>>      further variable (not as part of the variable "text"), so that
>>      Germans can format the command correctly. Can you help me with
>>      that?
>
> I this moment (swamped with a project application), all I can suggest
> is you look at org's time parsing codes for handling new agenda
> entries.  The text must be parsed somewhere...  If you use the same
> code within the advice, you should be able to pick off the times.
>
> I'll add this to my todo list but I won't get a chance to play anytime
> soon unfortunately.

Yes, I see. Same for me. I think we can live with this workaround for the
moment. Probably (hopefully), GoogleCL will be developped in a way more
suited in the near future. Until that happens, we can suggest people to
use an English setting of GoogleCalendar. Most org users will probably
use Google as a secondary method anyway.

>> That's also my work flow, except of using org-remember "k-r" instead of
>> "i". I like to have everything in one org-file. But I can get used to
>> keep my appointments in a separate diary file. I can refile them to the
>> appropriate places during the "weekly review" which, then, ends with the
>> upload of a new ics file.
>
> Can the diary file not be your all-in-one org file?

As far as I see, the entries created by the "diary method" can't be
configured according to level and exact location within the diary.org
file. The entries are written in a tree structure beginning with the
year at the beginning of the file. This would spoil the organization
structure of my main org file.

Thanks very much for your help,

Sven

  reply	other threads:[~2010-09-08  9:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-04 14:21 Adding entries to Google calendar Sven Bretfeld
2010-09-04 16:34 ` Eric S Fraga
2010-09-04 19:49   ` Sven Bretfeld
2010-09-05 11:48     ` Eric S Fraga
2010-09-08  9:04       ` Sven Bretfeld [this message]
2010-09-08 15:34         ` Matt Price
2010-09-08 15:58           ` Matt Price
2010-09-08 17:12           ` Stephen Eglen
2010-09-08 22:23             ` Matt Price
2010-09-09  9:25               ` Stephen Eglen
2010-09-10  8:33                 ` Eric S Fraga
2010-09-10 12:54                   ` Rémi Vanicat
2010-09-13  7:54                   ` Sven Bretfeld
2010-09-10  8:28               ` Eric S Fraga
2010-09-09  8:56           ` Sven Bretfeld
2010-09-10  8:36             ` 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=87pqwosj1s.fsf@rub.de \
    --to=sven.bretfeld@gmx.ch \
    --cc=e.fraga@ucl.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).