summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-01-28 08:42:26 +0000
committerjoey <joey@0fa5a96a-9a0e-0410-b3b2-a0fd24251071>2007-01-28 08:42:26 +0000
commit2af8a8d1fee73b54fcf28b1ef894010cc169be3e (patch)
tree13149c66254a3dbbfef6b75092b4263577c6ce40 /doc
parentf6f3f0ca4dd3f0603f13d36c897c7d862e422b4d (diff)
web commit by http://ethan.betacantrips.com/: response
Diffstat (limited to 'doc')
-rw-r--r--doc/todo/pagespec_expansions.mdwn21
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/todo/pagespec_expansions.mdwn b/doc/todo/pagespec_expansions.mdwn
index 14ca0d25e..e3302995a 100644
--- a/doc/todo/pagespec_expansions.mdwn
+++ b/doc/todo/pagespec_expansions.mdwn
@@ -18,3 +18,24 @@ A couple of suggestions for improving the usefulness of pagespecs:
> pagespecs match absolute by default. It would be nice to clear up that
> inconsistency somehow, it's on my little list of things in ikiwiki that
> arn't ideal. :-) --[[Joey]]
+
+I've looked at how to implement "./", yes, and I was a little hesitant
+to disturb the elegant implementation of pagespecs as it is now. That's
+why I wrote this todo item rather than just a patch :). As I see it,
+the simplest thing to do is check globs when building the pagespec
+expression and translate "./foo" to "$from.'/foo'" in the resulting
+expression, and then add the $from paramater to pagespec_match. This does
+require an API change for all plugins which use pagespecs but hopefully
+it should be minor. I will work on a patch tomorrow.
+
+My use case for "@" (which is kind of a crummy symbol, but whatever) is
+my [projects page](http://www.betacantrips.com/projects/). I want to inline
+"summary" or "introduction" pages that are exactly one level below the
+inlining page, but not tarballs or other junk that might be in
+subdirectories. (The issue is confounded here because of my index.mdwn
+patch, but the principle is the same.) I chose "@" because it's similar in
+physical shape to "*" but enclosed, suggesting limitations. I also thought
+it would be useful in simplifying hacks like in [[plugins/map]] but I see
+now that I was mistaken.. "four or fewer levels deep" would be
+"@ or @/@ or @/@/@ or @/@/@/@". Well, I think it has a certain appeal but
+I can see why it might not be much of an improvement :). --Ethan \ No newline at end of file