From f6d66d46845534da1b7677922193f24363f44003 Mon Sep 17 00:00:00 2001 From: "http://kerravonsen.dreamwidth.org/" Date: Thu, 3 Nov 2011 22:50:00 -0400 Subject: [PATCH] comment on the difficulty of trails --- doc/todo/Pagination_next_prev_links.mdwn | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/todo/Pagination_next_prev_links.mdwn b/doc/todo/Pagination_next_prev_links.mdwn index 8b3114340..f1c12d33f 100644 --- a/doc/todo/Pagination_next_prev_links.mdwn +++ b/doc/todo/Pagination_next_prev_links.mdwn @@ -27,4 +27,7 @@ Thank you > reduces the generic usefulness of typed links, though - in particular > you can no longer use "is part of trail A" in a PageSpec. --[[smcv]] +>>> Indeed, I know the problem; I ran into the same kind of thing with my [[plugins/contrib/report]] plugin and its `trail` concept. +>>> I simply had to declare that one couldn't use "trail" and "maketrail" options within the same report. That way, "maketrail" will add links in the "scan" pass, and "trail" will test for links in the "build" pass. That usually works. --[[KathrynAndersen]] + >> Do you have an example? --[[hendry]] -- 2.26.2