Hi thanks for all replies, sorry I forgot to mention that. That's exactly what I did; I ran mnemosyne from a script that appended the current date and time to a log file each time mnemosyne was run. The last entry before I had to reset date and time was 18:40 (--as confirmed by the log file--so that session obviously was okay); then at some point I had to reset date and time and only after that did I run mnemosyne again (22:00--as confirmed by the log file). This shouldn't have caused any problems, should it?
How exactly does mnemosyne determine whether a new day has come (I suppose it schedules cards on a day-to-day basis)? From what I have experienced it does not seem to be 24:00 (Before the date-time issue it must have been somewhere around 03:00 in the morning and my suspicion is that this has changed to somewhere around 20:00 after I had reset date and time). This would seem consistent with the way the program behaves, at least..... Kind regards Jakub On 3 dic, 21:00, Konrad Wojas <[EMAIL PROTECTED]> wrote: > On Tue, Dec 02, 2008 at 06:21:27PM +0100, Peter Bienstman wrote: > > It's hard to say what exactly happened. The safest would be to restore from > > a > > backup. > > It might be a good idea to store the last review time and check whether > the current time is in the past. This way a date that is accidently set > into the past would immediately be detected and a date set into the > future next time the date is set correctly. > > Cheers, > -- > Konrad Wojas --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mnemosyne-proj-users?hl=en -~----------~----~----~----~------~----~------~--~---
