On 4 Sep 2010 21:49:25 +0200, "Sven Bretfeld" <sven.bretfeld@gmx.ch> wrote:
> 
> Hi Eric
> 
> Eric S Fraga <ucecesf@ucl.ac.uk> writes:
> 
> > I'm not sure what you mean about complete.  It requires you to have
> > installed the Google command line tools (googlecl from Google Code).
> > However, this emacs lisp code is not what I would call full-featured
> > ;-)
> 
> There were several problems, most of which I have solved by now. First,
> I didn't set org-agenda-diary-file. So, calling "i" from an agenda-view
> merely opened the default diary file. That's why I wondered when
> exactly the advice comes into play. (Therefore I suspected the code to
> be possibly incomplete -- sorry, my fault.)

ah!  yes, the code is complete but the instructions are not.

> Now, the principle procedure works. Entries show up in Google after I
> added them with org-agenda-diary-entry. 
> 
> There is one thing left. You have structured the shell-command according
> to the American GoogleCL syntax. That's not working with the German
> locale. For a German GoogleCalendar the only syntax I found working is:

[...]

> 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 I did try-and-error: with and without the "am"
> and "um", with the English "on", with ISO formated dates etc etc. Except
> the above structure 'text am date um time' no combination works.
> 
> I fear, there are only two solutions:
> 
>   1. As a workaround I have set my GoogleCalendar to the American
>      locale. With that everything works fine.
> 
>   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.

> > However, the mechanism is there to support hooking into capture
> > specifically and possibly into org-time-stamp or org-schedule, say. 
> 
> I have tried to work out an advice to org-time-stamp and/or
> org-remember-finish today. But my Lisp is too weak. I couldn't figure
> out how to grab the data.

Maybe post what you did to this list and somebody might be able to
help?

> > I don't use Google calendar for scheduled tasks or deadlines so the
> > latter don't matter to me; I use it for appointments and my work flow
> > is that I always bring up the agenda view to see if my time is free
> > before making the appointment.
> 
> 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?