Jeremy Ruston

> I am tempted to open a new issue because I've just lost a long journal entry that I wrote earlier in the morning due to encountering this problem. >...

> Completely agree with @Dialga's reasoning - paraphrased, "new means new". The + also has accumulated baggage that drives my thinking -- I'm _adding_ / _creating_, not editing. Right, but...

Hi @CodaCodr having two separate buttons presents quite a cognitive load for users: * Understanding what to do if they don't see the button they expect * Being able to...

Thanks @rmunn, that's very clear. To answer your question, I think one would indeed need both `headerTemplate` and `header` for consistency. However, there are some downsides with this approach. The...

> Perhaps a simple solution would be for the list widget to have a built in count I think that is what is discussed over at #3384.

Hi @rmunn @saqimtiaz the subtlety is that these header and footer entries need to be outside the `/` of a list. That's the clue that these headers and footers can't...

Thanks @pmario. If you're finding it useful then yes, fixing it makes sense, and I'd welcome a PR.

It's a good idea. I don't think there are any backwards compatibility considerations because `@@foobar@@` at present doesn't do anything useful.

> Simple is better, so for me, the below is confusing It is a contrived example. I'm trying to show that the `/* comment */` syntax is not recognised within...

> 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...