This code kind of does that already. (Update: Just pushed an update to core-enabled to fix a problem in the variables discussed below.)
If you're running PS Core 6, then there are 3 helpful variables: $isWindows $isMacOS $isLinux To tell you what platform you are on. These variables don't exist in PS 5, so I faked them at the top, under the assumption that 5 will only run on Windows. There is also a platform separator character (long complicated name) which I put into $SEPARATOR and use everywhere in the new version (even though in many cases, but not all, PS can figure out the pathing). So far there haven't been any separate *.ini settings. The main thing is that users will need a different settings.ini file for each environment because of the pathing. But it kind of looks like if users use "/" for their pathing, and not absolute pathing (e.g. "C:/...") then it might work for both platforms without changes. Thanks! -- Mark On Monday, August 12, 2019 at 2:00:12 AM UTC-7, @TiddlyTweeter wrote: > > For instance, maybe platform dependent # INTERNAL SETTINGS might be moved >> to secondary scripts or *.\lib\win-internal.ini*, >> *.\lib\mac-internal.ini *& *.\lib\unix-internal.ini*? > > > My point about this is a wondering if we could enable *ONE system that > auto-supports 3 o/s*. > > So, for instance, a user who uses both Linux & Windows ONLY downloads ONE > set of PSCore scripts that can auto adapt to either run environment? > > Too ambitious? > > Simply my thoughts on now. > > TT > -- 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/df282a1c-51e0-44f7-9f17-1d3956b6c45d%40googlegroups.com.
