From 1faf9b08e16bde9b4b0d72620fcef79c715e64de Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 2 Apr 2010 17:37:38 -0400 Subject: idea --- doc/todo/allow_plugins_to_add_sorting_methods.mdwn | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'doc/todo/allow_plugins_to_add_sorting_methods.mdwn') diff --git a/doc/todo/allow_plugins_to_add_sorting_methods.mdwn b/doc/todo/allow_plugins_to_add_sorting_methods.mdwn index 67d85f6f8..e1e05e81c 100644 --- a/doc/todo/allow_plugins_to_add_sorting_methods.mdwn +++ b/doc/todo/allow_plugins_to_add_sorting_methods.mdwn @@ -63,6 +63,14 @@ NIH'd sorting mechanisms: >>>> is required to have params. They should be optional, >>>> to match the documentation and because most sort methods >>>> do not need parameters. +>>>> +>>>> I wonder if it would make sense to add some combining keywords, so +>>>> a sortspec reads like `sort="age then ascending title"` +>>>> In a way, this reduces the amount of syntax that needs to be learned. +>>>> I like the "then" (and it could allow other operations than +>>>> simple combination, if any others make sense). Not so sure about the +>>>> "ascending", which could be "reverse" instead, but "descending age" and +>>>> "ascending age" both seem useful to be able to explicitly specify. >>>> --[[Joey]] ## Documentation from sort-hooks branch -- cgit v1.2.3