Closed GoogleCodeExporter closed 9 years ago
I facing the same error as well.
I have commented the lambda code for google apps issue.
Really hope this has a quick advise or fix soon.
Cheers!
Original comment by donc...@gmail.com
on 8 Apr 2009 at 9:30
there is no support for adding to other calendars than default, this is a
REALLY ugly
workaround:
My only problem is that adding events with it is only supported to write to
default
calendar and that's not what I need to do. First go to the settings tab in
google
calendar -> calendars -> "the calendar you want to write to" -> check the Id at
the
Calendar Address (Calendar ID:
xxsdsdfcxxcvsefsxccvxcvxcv@group.calendar.google.com).
No to the very ugly hack to change from the default calendar in quick add, edit
the
gcalcli python script and change at row 832
self.gcal.InsertEvent(quickEvent,
# '/calendar/feeds/default/private/full')
'/calendar/feeds/xxsdsdfcxxcvsefsxccvxcvxcv@group.calendar.google.com/private/fu
ll')
And your submissions should go to the other calendar.
Original comment by henrik.a...@gmail.com
on 12 Mar 2010 at 12:08
This problem is still occurring with the latest version of gcalcli
Original comment by quid...@gmail.com
on 13 Nov 2010 at 9:26
Still happening ...
Original comment by ben.aus...@tcc-nc.net
on 11 Jan 2011 at 8:35
I've attached a patch that allows adding to non-default calendars (by posting
to the calendar specified if --cal is passed only once).
Original comment by alex.deh...@gmail.com
on 29 Apr 2011 at 9:40
Attachments:
Thank you for the patch. I will incorporate it soon.
Original comment by eda...@insanum.com
on 27 Jul 2011 at 7:19
Issue 53 has been merged into this issue.
Original comment by eda...@insanum.com
on 31 Jul 2011 at 5:27
Fixed. You can now quick add events to any calendar. This change requires
that a --cal option be used to specify which calendar.
Original comment by eda...@insanum.com
on 5 Aug 2011 at 10:03
I'm still having this problem on version 2.1.
Original comment by conner...@gmail.com
on 3 Nov 2011 at 11:44
Original issue reported on code.google.com by
paul%stl...@gtempaccount.com
on 10 May 2008 at 10:12