> All these can be done with the current markup. > ... > I have a strong preference to keep the current way of doing searches, and > to > enable the same way for the link= and the trail= parameters.
Yes, I chose simple examples to illustrate the concept rather than more complicated examples where the idea shows its power. So for an example that can't be done with current pagelist... (:pagelist (link=Category.A $:myvar=foo),(trail=GroupA.Mylist) order=name fmt=#simple:) This allows me to include all the pages in my manually created trail but also make sure that I haven't missed any other pages with a category of A and a PTV with a certain vlaue. Obviously the examples could get increasingly complicated, but hopefully this shows an example where it would be nice to have or/union capability. I, too, have a strong preference for keeping the current syntax on searches and I agree that it should be extended to the link= and trail= parameters. It would not be a bad idea to have this as a recipe rather than core, but in order for that to be accomplished the ParseArgs() function name has to be placed in a configurable variable (like $DiffFunction, etc.), at least in pagelist.php. Might that be a possibility in an upcoming release? (It would be nice in scripts/markupexpr.php as well where some enhanced functionality could be obtained.) It might be a good idea to have separate variables used in separate scripts to facilitate different types of functionality... -Peter _______________________________________________ pmwiki-users mailing list [email protected] http://www.pmichaud.com/mailman/listinfo/pmwiki-users
