It's simple. Start with the question: What's wrong with the default save? The only thing wrong with the default save, is that it doesn't save to the original directory and file name where you started. Outside of that, you can click save all day long inside of your browser session and everything works fine.
If you were to work around this by hand, whenever you started your TW session you'd go into your download directory, find the most recent version of your file, and copy it back into the original directory with the original file name. What the batch script does is to automate this. You click on the link and the script searches for the most recent version of your file, copies it back into the original directory, and then launches your TW script in your browser. There's no need to have a server running all day long. No executable. No plugins. No hidden data structures. As a bonus, you constantly have a back-up of your TW file much like you used to have in TWC. I picked a terrible title for my first post on this. I should revisit that sometime. Mark 3 - Your batch system for saving I read about before. It sounds interesting > but I'm still unclear how it works. > > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8bd851fc-c7e6-4169-9e13-533c0277bacd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
