search

Deadolus / googlecl

Automatically exported from code.google.com/p/googlecl
0 stars 0 forks source link

Dates in googlecl calendar add - complete mess! #529

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Create event in calendar with:  google calendar add "SIMPLE_EVENT_NAME 
2013-07-20 6:00AM-2:00PM" --cal="CalendarNAME"
2. visit https://www.google.com/calendar/ and... find your event on 2013-07-02! 
What the heck?!

I'd expect it to create event on 20th of July. 

Debian 6
google0.9.14
Python 2.7.3
gdata-python-client: 2.0.18

How am i expected to feed GoogleCL with dates so to be sure it's reliable and 
events get created on dates I expect them to? I can not imagine format easier 
to create with any kind of script and to parse it later than YYYY-MM-DD. Please 
provide users with reliable information on that. Parsing "human-like" input is 
great, if it works. If it doesn't give us at least straight info on how to use 
googlecl so it's reliable.

The same things happens to hours - 24h clock-format is hard to misunderstand, 
but googlecl happens to do it well, but at least feeding it with AM/PM and 12h 
clock-format works in this case so it's kind of work-around.

Please consider it pretty annoying.

Kind regards

Trulynlooking forward for reliable version of GoogleCL and clear documentation 
on it!

Regards,
L.

Original issue reported on code.google.com by leszek.r...@gmail.com on 25 Jun 2013 at 9:50

GoogleCodeExporter commented 8 years ago 
What is more worth mentioning: Adding events with the very same command with 
(some) other dates works like a charm. 
But some of dates seem to be truly unbearable for GoogleCL.

Original comment by leszek.r...@gmail.com on 25 Jun 2013 at 6:33

GoogleCodeExporter commented 8 years ago 
and off we go... another "white rabbit" to chase for:
google calendar add "EVENT_NAME 2013-11-21 6:00am to 2:00pm" 
--cal="CALENDAR_NAME"

and where do we get our event? on 2013-11-02 !

and how come that almost-the-same command:
google calendar add "THE_VERY_SAME_EVENT_NAME 2013-11-20 6:00am to 2:00pm" 
--cal="THE_VERY_SAME_CALENDAR_NAME"

worked just fine creating event on 2013-11-20?!
Where did that come from?
What is the logic of above?

Can anyone please take a look at this issue. It's driving me crazy.

Original comment by leszek.r...@gmail.com on 5 Sep 2013 at 9:55