I think that the problem with the windows commands is from all of the commands sharing the same io streams. I can add an option to have a command run with its own terminal instead of in the shared terminal with Bob and that may help. The downside is that it may spawn a new window for each script that runs.
I am not sure what the differences between bash and the windows command prompt are that may cause this but that is the only thing I can come up with that may fix it. TiddlyTweeter, All of the wikis share the same settings that you can only edit from the root wiki. The settings go with the node process, not with the specific wiki. I looked into per-wiki settings but so far I haven't run into a situation where it would be helpful. There is a tiddler called $:/WikiName that has the name of the current wiki that is used by the back-end, so you can just transclude that instead of defining it in the macro. And the buildHTMLWiki message can take outputFolder and outputName parameters that you can use to set the location of the generated html file so you may not need to manually copy them after they are created. Other than that I think you are doing it about as efficiently as is possible at the moment. Have you run into any troubles with the generated html files? I had seen some strange behaviour where I wasn't always able to import them into other wikis by dragging and dropping the html but I haven't been able to test it out much yet. -- 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/45e3c82f-57dc-4446-8142-8de90199567a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
