response
parent
861080b918
commit
10f4695abd
|
@ -165,7 +165,6 @@ That earlier version of the branch is also available for comparison:
|
||||||
>>>>>>> I've kept the semantics from `report` as-is, then:
|
>>>>>>> I've kept the semantics from `report` as-is, then:
|
||||||
>>>>>>> e.g. `sort="age -title"`. --s
|
>>>>>>> e.g. `sort="age -title"`. --s
|
||||||
|
|
||||||
>>>>>
|
|
||||||
>>>>> Perhaps we could borrow from `meta updated` and use `update_age`?
|
>>>>> Perhaps we could borrow from `meta updated` and use `update_age`?
|
||||||
>>>>> `updateage` would perhaps be a more normal IkiWiki style - but that
|
>>>>> `updateage` would perhaps be a more normal IkiWiki style - but that
|
||||||
>>>>> makes me think that updateage is a quantity analagous to tonnage or
|
>>>>> makes me think that updateage is a quantity analagous to tonnage or
|
||||||
|
@ -217,6 +216,10 @@ Unfortunatly, I think that c is closest to the new implementation.
|
||||||
> is sorted. Or, it might be useful to do the filtering first, then
|
> is sorted. Or, it might be useful to do the filtering first, then
|
||||||
> sort the sub-list thus produced, then finally apply the limit? --s
|
> sort the sub-list thus produced, then finally apply the limit? --s
|
||||||
|
|
||||||
|
>> Yes, it was deliberate, pagespec matching can be expensive enough that
|
||||||
|
>> needing to sort a lot of pages seems likely to be less work. (I don't
|
||||||
|
>> remember what benchmarking was done though.) --[[Joey]]
|
||||||
|
|
||||||
## Documentation from sort-package branch
|
## Documentation from sort-package branch
|
||||||
|
|
||||||
### advanced sort orders (conditionally added to [[ikiwiki/pagespec/sorting]])
|
### advanced sort orders (conditionally added to [[ikiwiki/pagespec/sorting]])
|
||||||
|
|
Loading…
Reference in New Issue