I feed that the existing use of bang in pagelist selections is either low or non existent,<div>in part because the documentation doesn't mention it strongly, and all examples user the hyphen.<br><div>Community can correct me on this ...</div>
<div><br></div><div>The new markup could be introduced initially as an option that has to be switched on, thus not breaking anything.</div><div>Switching the new feature on would mean</div><div><ul><li>bang no longer worked as negation in pagelist parameters</li>
<li>the new link=!MyCategory pagelist parameter functionality would be enabled.</li></ul><div>As part of a future major release, or after significant time, it could become the default behaviour</div><div>and in fact could be the default behaviour in new wikis.</div>
<div>The indexing of [[!MyCategory]] can be introduced in any case.</div></div><div><br></div><div>My thoughts</div><div><br></div><div>Simon</div><div><br><br><div class="gmail_quote">On 6 March 2010 10:06, Petko Yotov <span dir="ltr"><<a href="mailto:5ko@5ko.fr">5ko@5ko.fr</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">On Thursday 04 March 2010 10:03:12, Peter Bowers wrote :<br>
> On Thu, Mar 4, 2010 at 7:40 AM, Petko Yotov <<a href="mailto:5ko@5ko.fr">5ko@5ko.fr</a>> wrote:<br>
> > I now see a problem of which I haven't thought before -- with other<br>
> > parameters like name=!Name or group=!Name the "!" means "NOT Name" so<br>
> > link=!Name may be confusing and a bad idea. :-(<br>
> > Especially if at some point we change the link= parameter to accept<br>
> > multiple page names like link=Page1,Page2,-Group3.* . Hmm...<br>
...<br>
><br>
> What if we went with something like this:<br>
> link=^!^mycat<br>
> -or-<br>
> link=(!)mycat<br>
> -or-<br>
> link=\!mycat // kind of like escaping the !...? [1]<br>
<br>
This is exactly the thing I'd like to avoid -- if there is an inconsistent and<br>
un-intuitive implementation for a new feature request, we add more complex and<br>
un-intuitive markup to fix its problems. :-)<br>
<br>
I feel that I was wrong about this -- I don't want to add a feature without<br>
enough thinking, and regret it later when it could prevent us to do a more<br>
important change. When I see that I'm wrong I change.:-) Good thing that it<br>
wasn't released.<br>
<br>
While there are users from the community who want this feature, I'm not sure<br>
we have a consensus, ot even a majority. The implementation requires<br>
substantial changes to the core and I feel that what we have now is not really<br>
a good, globally logical solution. Also, a couple of bugs need to be fixed and<br>
released asap.<br>
<br>
For these reasons, I'll suspend the feature request (PITS:00447) until we find<br>
a better way to deal with it.<br>
<br>
Thanks,<br>
Petko<br>
<br>
_______________________________________________<br>
pmwiki-users mailing list<br>
<a href="mailto:pmwiki-users@pmichaud.com">pmwiki-users@pmichaud.com</a><br>
<a href="http://www.pmichaud.com/mailman/listinfo/pmwiki-users" target="_blank">http://www.pmichaud.com/mailman/listinfo/pmwiki-users</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>____<br><a href="http://kiwiwiki.co.nz">http://kiwiwiki.co.nz</a><br>
</div></div>