I like what you're doing with the scripts, TT -- Your batch script is really neat and organized. I had forgotten that crazy way that windows batch scripts use errors to make choices.
Re your ps script, I don't see where "downloaddir" gets used -- am I missing something? Re the woofs, I had been thinking of having a separate configuration file. It might be easier to implement in powershell as a JSON file. Admittedly, your configuration file would be easier to read. Do you think JSON will be adequate? Re stemming ... I'm not sure what the alternative is. It's the download saver that sort of forces the approach. Or are you just saying it's easier on the user to specify a single file/path at once? I can see that. I just want the user to think a little bit about the stem issue. They might not realize that "mytiddlywiki.html" will overwrite "mytiddlywiki5.html". But maybe just emphasizing this in the documents is sufficient? I'm not sure what exe brings to the table. I guess it's a way to reduce every thing (initially) to a single file. But the user will still need to hand-edit a configuration file, so does it matter? Windows now has zip ability, so it's possible to package things without shipping as an executable. I'm guessing that an unsigned exe will create alarm bells with a lot of AV software out there. Any problems with Windows Defender? The charm of a simple ps script is that anyone can eyeball it and see that it's mostly harmless. Not so much with exe's. Thanks! On Tuesday, June 25, 2019 at 2:35:11 AM UTC-7, @TiddlyTweeter wrote: > > Mark S. wrote: > >> I'm not a PowerShell aficionado, so even a short script takes some time. >> > Dear Non-Aficionado > > As the 3-Legged Dog in this tiny ship of interest I am a Seriously Hobbled > Participant at the mainmast. Trying to be competent is a heavy burden. > > After walkies with the code and exhausting trials with my master I can > hazard a few barks ... > > > woof 1 -- the settings part is fine for one or two wiki; > > > > woof 2 -- the settings will likely be error prone (they will get messy, > especially with long paths) if he has more than a few wiki, which he does; > > > > woof 3 -- the "stemming" approach, rather than full specification (full > path) of the Target Cat, may prove troublesome for Support Services as > unanticipated overwrite restores remain possible; > > > > woof 4 -- the essential dogfood point is that, maybe, "Nine-Lives" > (provisional name), needs an additional first routine that can read a > config file that *parses exact full addresses* and assembles an array of > them for the main PS1? From, e.g. something like an "ini" file ... > > > [wikis] > C:\mylargedog\smallvariant\doggie\rover.html > C:\myhates\thosecats\gingerrrr.htm > > [download-dir] > C:\User\Shep\Downloads > > [timing] > 60 > > Yours in walkies (slightly off-kilter) > Shep > -- 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/41d0b492-6cf2-45a5-93b1-af95534b281e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
