| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Lukas Fleischer <calcurse@cryptocrack.de>
|
|
Signed-off-by: Lukas Fleischer <calcurse@cryptocrack.de>
|
|
|
|
Short forms are only accepted in interactive mode (e.g. when using the
"Go to" function, editing a recurrent item's end date, and so on).
Samples: "1/1/30" for "01/01/2030", "26" for the 26th of the currently
selected month/year or "3/1" for Mar 01 (or Jan 03, depending on the
date format) of the currently selected year.
|
|
|
|
turn of year (submitted by Lukas Fleischer, thanks!).
|
|
|
|
|
|
:'( Anyway, thanks Kamil for feedback
|
|
|
|
|
|
fixed a 2-years old bug that made repeated items with exceptions to load
uncorrectly in some cases (thanks Jan for reporting it)
|
|
memory usage
|
|
|
|
|
|
reporting them)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
account date_t type
|
|
|
|
|
|
|
|
|
|
to handle item state
|
|
recur_apoint_switch_notify() created
recur_apoint_write() and recur_apoint_scan() updated to handle item state
|
|
|
|
|
|
|
|
|
|
|
|
again
|
|
|
|
bugfix in recur_apoint_check_next(): a recurrent appointment is now properly notified
bugfix in recur_item_inday(): apopintments now keep a correct start time when repeated
|
|
from race conditions
recur_apoint_llist_init() created
|
|
|
|
|
