search

FlorianHeigl / googlecl

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

--date=YYYY-MM-DD in calendar only sets the start of a date range. #71

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Enter "google calendar list --date=YYYY-MM-DD"

What is the expected output? What do you see instead?
Expected: Only the events on YYYY-MM-DD.
Actual: All events on YYYY-MM-DD and future dates.

Setting a range, eg with "--date=2010-06-21,2010-06-22" works as expected, but 
without an end date set, the option is treated as an open-ended range instead 
of a single day.

What version of the product are you using? On what operating system?
0.9.5.1, installed on Ubuntu 9.10 via the deb file.

Please provide any additional information below.

Original issue reported on code.google.com by arancayt...@gmail.com on 19 Jun 2010 at 8:50

GoogleCodeExporter commented 9 years ago 
The version should be "0.9.5"; I misread the file name's "0.9.5-1_all.deb".

Original comment by arancayt...@gmail.com on 19 Jun 2010 at 8:52

GoogleCodeExporter commented 9 years ago 
In fact the problem is worse than that because it doesn't bring back ALL future 
dates only a certain number up to an undefined limit. In other words if I were 
to set a range of "google calendar list --date=1996-01-01,2011-01-01" or 
"google calendar list --date=1996-01-01" it only brings about 6 months of 
entries or anything between 200 to 500 lines of text when there should be 2214 
entries.

Original comment by jim.t...@gmail.com on 19 Jun 2010 at 11:00

GoogleCodeExporter commented 9 years ago 
I've attached a patch to fix that behavior. You can still set a range with 
"--date YYYY-MM-DD," (note the trailing comma). A comma-less value will give 
only one day.

Jim, could you file that problem in a separate issue?

Original comment by tom.h.mi...@gmail.com on 19 Jun 2010 at 9:59

Attachments:

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r250.

Original comment by tom.h.mi...@gmail.com on 19 Jun 2010 at 10:01