Hi TiddlyTweeter, On Friday, May 24, 2019 at 2:29:48 AM UTC-7, @TiddlyTweeter wrote: > > Ciao Mark S. > > It works! :-) > > Some initial comments . > > *Tested on ...* > > Windows 10 64-bit tablet > > PowerShell: 6 > > Browsers: Vivaldi, Firefox, Edge, Chrome, 2 other Chromium > > > > Wow -- very thorough. I should say, your setup outstrips mine. I think I'm still on PS 4, Windows 7. Every day my Google News feeds reports problems people are having with updates on Windows 10. Makes me wonder if I should stick with Windows when support for 7 is dropped.
> TEETHING PROBLEMS > > -- PowerShell would not run the script till I ran the (session only) > command ... > > "Set-ExecutionPolicy -scope CurrentUser -executionPolicy Unrestricted" > > > How did you discover the secret recipe? I wonder if that's a PS6 thing? I imagine that it's possible to set this in your profile. > > BROWSERS -- SMALL ISSUE > > To my surprise not all modern browsers save the version number exactly > the same way. Both "name (2).html" and "name(2).html" occur. > > > Well, they should both match the stem, so it should still be OK. > STEMMING > > I don't understand how to do it but I think the stemming issue with > possible overwrite could be avoided by using a regular expression rather > than the general wildcard? > This looks like it might work .... > > "$stem(\s*\(\d+\))?$" > > But I'm unclear how PowerShell invokes the matching it can do ( > https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_regular_expressions?view=powershell-6 > ). > > > That document explains how to do string matching. File globbing looks like regular expressions, but it's not. Possibly it would be possible to insert code that analyzes the output as strings. So one line of code would become 10 ;-) but it's unclear -- is there an actual problem that would be fixed by this approach? > INSTANCES? > > Just a thought for later. Based on my working practice. > > In actual usage I'd be more likely to set "$waitSeconds" to 600 since I > don't write that much. > > I've been running several days with 180 seconds. I assume that the smaller the number the larger performance hit. But that hit is likely still way less than the browser itself. On my system it's less than the node.js instance. And uses a fourth of the internal memory. > What I'm interested in knowing is if one could run a second instance of > the script--identical except it just does a restore of wiki and then exits? > > For the moment you could just stop and restart the script. It should be possible to add an argument to the code so you could run it like 'tw_launch_all.ps1 -mode="onetime" ' and it would run just once. > > FURTHER TESTS > > --- I will play with running it via a batch file. > > Here's the code I used to launch from a batch : powershell -executionpolicy bypass -File .\launch_all_tw.ps1 It might work for you too. Thanks! -- Mark -- 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/45e348ae-b677-44c9-9381-e03528576941%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
