I agree… it just looks less messy too. The syntax order (
.) also maps better to the order of
descendant-or-self::. The only issue is that I have with it is that the
. character visually mixes in with other content characters to me and still looks a bit messy.
I expect these kinds of searches to become more important going forward, and I want a really clean syntax…
In the next release I’m going to be switching the focus/hoist to go back to what I hard originally, and only show the children of the hoisted item. I know it’s not what people are used to from TaskPaper 2, but I think it’s cleaner conceptually and avoids a bunch of interface problems and special cases.
But when I make that change I also want to provide some clean way to do
descendant-or-self:: searches so people can get the TaskPaper 2 behavior if they want. With that in mind what do people think about changing the
// shortcut to map to
descendant-or-self:: instead of mapping to
descendant::. It diverges from the Xpath spec, but I think is the preferable default for TaskPaper?