|
> so for agent the prestring should be 'subject:('? > Send me an updated setformat.xml 8).....I will include it in the next version.
Here's the Agent line from my xml file
I've renamed it to "Forte Agent (Global-Search Input)" so people should have a better idea what to do with it. With both Agent & Newsbin there are size limits to the search string with Agent it 999 bytes and with Newsbin it's 30000 bytes - so if a lot of things are missing it may require a lot of manual editing work if Agent is used in such cases. In those cases it would obviously be better to use Newsbin and do a search and replace to escape the special chars.
> I checked official regular expression docs and yes, it's not officially possible > to disable regular expression parsing for a part of the string.... > I could add a flag to the xml to escape the characters...but then you will lose > the ability to keep regular expression terms in the 'string' attribute at > all.... So I guess we can't really get around regular expression parsing. >
It's a shame but I am inclined to agree and it's a lot of work...I can't believe such a major expression library hasn't got a way of handling a string 'as-is'...but sadly having searched for hours it's obvious that it's just not possible.
|