I lied. See regexPlugin209_091023.zip in http://tech.groups.yahoo.com/group/power-pro/files/0_TEMP_/AlansPluginProvisional/
chooses PCRE_NOTEMPTY or PCRE_NOTEMPTY_ATSTART depending on version of PCRE. Re odd error messages. Did uyou by any chance download any of the recent exe-only changes Bruce left a webeddie? After last one, an entry in my New Window command list, long dormant, started to fire -- I only knew because I'd but a debug statement in a command item ages ago, which suddenlt started firing. Dunno if that;'s to do with the exe update, or phase of moon, or your error messages from my plugins. --- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote: > > > > --- In [email protected], "Sheri" <sherip99@> wrote: > > > > Works fine, but causes plugin version 2.09 to be incompatible with earlier > > releases of PCRE. Perhaps during initialization, the plugin should refuse > > to load if the PCRE library version is less than 8.00. Alternatively, you > > could set some variable during initialization (equal to either > > PCRE_NOTEMPTY or PCRE_NOTEMPTY_ATSTART) and use that in the "options = " > > line above. > > Sure, can do that. Not til next week, though. > > Re problem below: if it continues to occur, back off to earlier version of > refgex (and com, if you installed that). Let me know if it goes away. > > > Don't know if related to recent changes to the regex plugin, but I've seen > > the following inexplicable message a few times today. I wasn't testing > > scripts or anything at the time. > > Definitely looks like a problem with one of my plugins: "OK" is coming back > where a handle was expected, and then used in some script that runs regularly? > > > --------------------------- > > PowerPro > > --------------------------- > > Invalid use of period: cannot load plugin, invalid handle value, or invalid > > function: > > --------------------------- > > OK > > --------------------------- > > > > Regards, > > Sheri > > >
