Closed GoogleCodeExporter closed 9 years ago
Try
google calendar add "Some event in future 2010-07-01"
Original comment by xinl...@gmail.com
on 20 Jun 2010 at 7:14
Ok this works. My bad, but according to man pages date is specified with -d
option.
Original comment by kowalski...@gmail.com
on 20 Jun 2010 at 1:30
Sorry for the confusion. The calendar add uses the "Quick Add" feature to add
events, and does not take any options other than --cal to specify a non-primary
calendar.
It does feel natural to specify a date with that option, though. I'll look into
supporting it for the add task.
Original comment by tom.h.mi...@gmail.com
on 20 Jun 2010 at 8:39
Upping priority, since this is a necessity for non-English calendars.
Original comment by tom.h.mi...@gmail.com
on 4 Oct 2010 at 8:00
Original comment by tom.h.mi...@gmail.com
on 25 Oct 2010 at 9:45
It should be noted that googlecl will add an event to the primary calendar
unless --cal is specified, but regardless of what that primary calendar is
actually titled, googlecl will just assume it's a user's email address. I've
changed the name of my primary calendar, but googlecl still insists it's my
email address when I list events without giving the --cal flag.
Original comment by nvsbl.mo...@gmail.com
on 26 Oct 2010 at 5:27
Alright, I think this functionality is finally ready as of r480.
There's a whole lot more that --date will accept:
10/30
4:59
06/15/11 at 6
10/22/2012 @ 12:53pm
Aug 23 2020 at 5pm
ranges specified with a ',' are still valid, too. And you can now specify
durations:
google calendar add "my event" --date 4pm,+3
will act like you used a quick add text of "my event at 4pm until 7pm"
NOTE: Specifying --date will DISABLE quick add. so "my event on the moon" will
actually be called "my event on the moon", not "my event" that takes place "on
the moon".
The README.txt in the trunk has all the details. I've also attached a patch
that should work -- you'll definitely get complaints about finance.py that you
can safely ignore.
Original comment by thmil...@google.com
on 28 Oct 2010 at 8:29
Attachments:
Original issue reported on code.google.com by
kowalski...@gmail.com
on 19 Jun 2010 at 11:12