In that event, how about making backups a bit more configurable? I for one would be fine if backups only generated once every day or every 12hrs or something (IF there were changes) -- but ultimately -- I do not rely on my applications to backup my data... I rely on my backup services to safely manage and restore my data.... (As should anyone concerned with data corruption)
With mudlet however (since apparently it doesnt write to disk when you edit things) this becomes impossible... needlessly complicating things by making an extra backup routine seem necessary.... -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1215034 Title: save profile - less than idea behavior Status in Mudlet the MUD client: New Bug description: Recently my windows manager crashed and it seems despite having been running for several weeks, my latest changes to my mudlet scripts were not saved.... While i understand the "save profile" button solves this, it seems rather unintuitive that mudlet does not save the profile when you are making large changes to the triggers and such when you close the script window or when those triggers become active at least. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1215034/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mudlet-makers Post to : [email protected] Unsubscribe : https://launchpad.net/~mudlet-makers More help : https://help.launchpad.net/ListHelp
