The Doctor What

4 Comments

1. Joshua Rodman
   Posted 2008-12-3 at 3:50 pm | Permalink

   Hey, one of the reasons I use ItsAllText is because the browser is
   unreliable. It might crash, it might lose my session and throw my text
   away.

   Unfortunately, ItsAllText doesn’t really clean this up all the way. If
   ItsAllText hands the text back to the browser, and then the browser crashes,
   ItSAllText has already deleted the data.

   Can I disable the delete? I’m perfectly capable of cronning a cleanup.

   -josh

2. docwhat
   Posted 2008-12-3 at 8:27 pm | Permalink

   Hi Josh!

   Actually, it isn’t deleted. All the files are marked as “temporary” by firefox. If it crashes, temporary files aren’t cleaned up.

   You should be able to right click on the “edit” button and select “Edit using previous ‘.txt’ content” (obviously .txt will be whatever extension you edited it as).

   If something has changed so that temporary files are being deleted even after a crash, then I’ll take a look at it.

   Ciao!

3. Joshua Rodman
   Posted 2008-12-4 at 1:57 pm | Permalink

   That isn’t the issue.

   Here is the timeline.

   1 - User hits edit.
   2 - gvim session appears
   3 - user edits file in gvim session, and writes the file out, exiting the editor
   4 - the addon somehow causes the edit area to flash yellow, indicating the edit is received.
   5 - something dumb happens like the browser crashes, or goes to a new page automatically and crashes without submitting the text, or the session is lost and some javascript causes the page to change.

   Maybe I misunderstand and there’s really a step 6 where I restart the
   browser following the Dumb Thing, and that causes it to delete all the temporary files? I don’t know what the timespan of these files is,
   but I’d prefer it to be infinite.

4. Joshua Rodman
   Posted 2008-12-10 at 12:34 pm | Permalink

   You know, I should just configure vi to make backup files based on the path with an aucommand for my unusual feature request.