> I think it would make sense to have "pagespec" in the name somehow.
-> > Good idea, how about `pagespecalias`? — [[Jon]]
+>> Good idea, how about `pagespecalias`? — [[Jon]]
->
> No, the strict/warnings does not make me puke. Have you read my perl
> code? :-P
>
>> Useful indeed! --[[Joey]]
->>> I've tweaked my patch in light of your above feedback: The plugin has
->>> been renamed, and I now validate keys. I've also added documentation to
->>> the branch. I haven't read rubykat's code properly yet, and don't have
->>> access at the time of writing (I'm on a beach in Greece ☺), but I expect
->>> it would be possible to extend what I've got here to support defining the
+>>> I've tweaked my patch in light of your above feedback: The plugin has been
+>>> renamed, and I now validate keys. I've also added documentation and tests
+>>> to the branch. I haven't read rubykat's code properly yet, and don't have
+>>> access at the time of writing (I'm on a beach in Greece ☺), but I expect it
+>>> would be possible to extend what I've got here to support defining the
>>> aliases in a PageSpec, once the dependency stuff has been reasoned out
>>> properly.
>>>
>>>> whatever you like ☺ I like some of the enhancements you've made, but
>>>> having the aliases/subsets/"things" work in any pagespec (inside map, or
>>>> inline) is a deal-breaker for me. — [[Jon]]
+
+>>>>> I'm a bit confused by your statement "having the aliases/subsets/"things" work in any pagespec (inside map, or inline) is a deal-breaker for me".
+>>>>> Do you mean that you want them to work in any pagespec, or that you *don't* want them to work in any pagespec? -- [[KathrynAndersen]]
+