Did you find any actual downside? Once we have a function in place, it shouldn't be hard to implement. We just have to "sanitize" the four+ directory types. Unless of course ... it breaks relative addressing or something.
Thanks! On Saturday, August 3, 2019 at 6:43:22 AM UTC-7, @TiddlyTweeter wrote: > > Ciao Mark > > I'm not sure its worth it on bespoke %env%. I toyed around a bit. I kinda > felt it was bending a bit backwards on it. A user who needs that special > path only needs enter it once, (literally) right, anyway in Polly settings? > So its seems like overkill to worry the point? But maybe I''m missing > something? > > But I do think automating a default o/s determined downloads dir does have > traction in that its a common situation and (hopefully) makes immediate > sense to many users (when we have more than two). > > TT > > On Friday, 2 August 2019 21:33:08 UTC+2, Mark S. wrote: >> >> That would be the original request. After some research, it looks like if >> we bring in the settings like this: >> >> $backupdir= $general["backupdir"] >> $backupdir= >> [System.Environment]::ExpandEnvironmentVariables($backupdir) >> >> (which we would probably put into a function to simplify)* >> >> And have a setting entry like: >> >> backupdir=%userprofile%\Downloads\polly-backup >> >> That it works. Maybe you want to try that and see what you think. Is the >> extra complexity >> worth the results? >> >> Thanks! >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/c12c3927-fdb0-4522-9726-1233b9f50b4b%40googlegroups.com.
