Jed Further to the posts before (below) ... I just noticed that if you start Windows apps using scripts that when you terminate Bob it also terminates those apps. (FYI, they are not "calls" which would pause Bob, they have their own memory space and run fine & don't interfere).
Could there be way to have flag on script launch that created a separate process that isn't a child of Bob? Such that it could persist after Bob expires? Hope this is clear! Josiah On Sunday, 27 May 2018 13:59:20 UTC+2, @TiddlyTweeter wrote: > > Jed Carty wrote: >> >> 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. >> > > Having a separate terminal window on Windows could be useful. But not if > it changes the current behaviour. As an additional feature, Yes, > definitekly. As a standard way of running, No. Reason being it complicates > things for more routine procedures where a simple batch file will do the > job already in the primary console. > -- 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/4d24086f-d258-423f-90d9-b03e5ca10349%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
