Robin Munn

#6897 will fix the problems with using the `list` field. The second bug report in this issue, where you get a "TypeError: can't access property `indexOf`, list is null" message,...

Which makes perfect sense; the issue was that I called `tiddler.getFieldList`, knowing that it called `parseStringArray` and thinking that that meant I was free to modify the resulting array. I...

#6897 has been merged now, which will fix most of the problems reported by this bug. There is one remaining problem, which is that if you try to use a...

Before merging this PR, I think it's important to hammer out the details of the syntax. It's probably best if we reuse an existing syntax, like jsonpath or [jq](https://stedolan.github.io/jq/manual/), as...

It's *almost* met, but not quite. I want to be able to produce something like the following: ```html Header One Two Footer ``` Which renders as: Header One Two Footer...

This should become possible to implement myself once #6666 is implemented: I'll be able to write a `$$headed-list` widget looking something like this: ```plaintext \widget $$headed-list(filter, header) \end ``` **Edit:**...

If there's a chance that the comment syntax could overlap with tiddler titles / tags / whatever that people have already made, then one possible solution could be to require...

> There's a lot less typing in `//` comments, and a little less typing in `/*` comments. Having multiple comment formats makes it easy to allow people to comment out...

P.S. Another VERY good argument in favor of `//` is that it doesn't complicate parsing. With any comment that has start and end markers, you run the risk of mis-parsing...

@saqimtiaz I did think about a filter run prefix, because it would make perfect sense to interleave the results so far with the results of "this filter expression right here"....