On Wed, Nov 11, 2009 at 12:06 AM, yy <yiyu.
...@gmail.com> wrote:
> 2009/11/10 Uriel <urie
...@gmail.com>:
>> This solves some of the issues, but as I noted in irc: I still think
>> it should not touch the generated html and instead manipulate the
>> markdown, and it breaks the proper chronological sorting of dir
>> "aggregations".
> this version of blagh.patch should work, it is a bit simpler. you want
> blagh.donottouchthehtml.patch, but if you use that you will finish
> with two almost identical html outputs in the cache for every file
Thanks, but I'm a bit mystified as to what the
| fltr_cache cat
does, as far as I can see it doesn't really do anything useful, in
which case the patch is the obvious patch, but which I had not
implemented as I wanted to avoid calling fltr_cache/$formatter for
every single post.
Anyway, maybe we should implement the obvious fix, but given that it
is not too critical (references are fortunately rarely used, and I was
considering just forbidding their use altogether), and I was hopping
for something that would actually cache the work done inside the loop,
to do that factoring things out into an external function is the way
to go, but fltr_cache might need to be extended to allow taking
multiple files and/or dirs instead of just one.
Thanks again for the effort though :)
uriel
> --
> - yiyus || JGL . 4l77.com
