let's eliminate some of the variables, here. explicitly specifying the date with the command:
evolution calendar:///?startdate=20060608T114022
starts evolution with the correct date (8 june 2006). however, omitting the time portion with the command:
evolution calendar:///?startdate=20060608
starts evolution with the incorrect date (*7* june 2006). a safe workaround could be having the calendar applet include the time on its command line for starting evolution.
let's eliminate some of the variables, here. explicitly specifying the date with the command:
evolution calendar: ///?startdate= 20060608T114022
starts evolution with the correct date (8 june 2006). however, omitting the time portion with the command:
evolution calendar: ///?startdate= 20060608
starts evolution with the incorrect date (*7* june 2006). a safe workaround could be having the calendar applet include the time on its command line for starting evolution.