From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gez Subject: Idea: insert "current sort order" property Date: Fri, 7 Oct 2011 17:02:58 +0200 Message-ID: Reply-To: suleika@gmail.com Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=0016e6d7e100c7699a04aeb6bdb9 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:41434) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RCByK-0001gP-CX for emacs-orgmode@gnu.org; Fri, 07 Oct 2011 11:04:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RCByH-0007rN-Ny for emacs-orgmode@gnu.org; Fri, 07 Oct 2011 11:04:24 -0400 Received: from mail-wy0-f169.google.com ([74.125.82.169]:44969) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RCByH-0007qf-Co for emacs-orgmode@gnu.org; Fri, 07 Oct 2011 11:04:21 -0400 Received: by wyh15 with SMTP id 15so775767wyh.0 for ; Fri, 07 Oct 2011 08:04:19 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --0016e6d7e100c7699a04aeb6bdb9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable What I'm imagining is a command executed on a headline to insert a property into each of its children "fixing" the current order; something like ":sorted:01", ":sorted:02" etc. Ideally there would be a prompt for the property key (or part of it) so that there could be more than one such property for a particular headline, but with the option to simplify the usage and consistency by having just one property key as a default and no prompt. One of my uses of org-mode is to list songs (Lieder) that I am currently working on, and I mark them up with special todo states and tags relating t= o my workflow - e.g. findscore, translate, memorise etc. I've also been know= n to add properties such as 1st line text (if different from title), poet, an= d pagenumber. While I'm dealing with a list of repertoire (there's a lot of bitty admin involved!) I've found it useful to sort alphabetically, by TOD= O state and by these properties, but I'd like to be able to retain the order in which the songs will be performed. I know I could manually add such a property to each headline myself but I'd really love to be able to quickly "fix" the order of my sorted headings by automating a ":sorted:" property. Another use I can imagine for this is when juggling an outline, one could "fix" an order that reads well, and then play around with it to see how it might flow better, knowing that it would be easy to return to the last preferred sort-order - like a rollback. During the last few weeks I would have made use of this not only when working on songs, but also when designing song programmes and writing my resum=E9. If a sorted headline got moved to a new parent its sort-order might be a duplicate one of its siblings, but I don't really see that as a problem - the user knows it's "only text" after all. I don't know whether it might b= e desired to similarly fix the sort-order of 1st level headlines; perhaps the command could act per current file, with a < to narrow down to the current tree. I'm also not sure how to deal with larger numbers - 01-99 seems like a good default but could one have an option for 001-999? I also wonder about adding the property to more than one level at a time, but might that be a bit much in terms of affecting performance? Does anyone else see this as potentially useful? Gez GNU Emacs 23.3.1 and org-version 7.7 --0016e6d7e100c7699a04aeb6bdb9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable What I'm imagining is a command executed on a headline to insert a prop= erty into each of its children "fixing" the current order; someth= ing like ":sorted:01", ":sorted:02"=A0 etc.=A0 Ideally = there would be a prompt for the property key (or part of it) so that there = could be more than one such property for a particular headline, but with th= e option to simplify the usage and consistency by having just one property = key as a default and no prompt.=A0

One of my uses of org-mode is to list songs (Lieder) that I am currentl= y working on, and I mark them up with special todo states and tags relating= to my workflow - e.g. findscore, translate, memorise etc.=A0 I've also= been known to add properties such as 1st line text (if different from titl= e), poet, and pagenumber.=A0 While I'm dealing with a list of repertoir= e (there's a lot of bitty admin involved!)=A0 I've found it useful = to sort alphabetically, by TODO state and by these properties, but I'd = like to be able to retain the order in which the songs will be performed.= =A0 I know I could manually add such a property to each headline myself but= I'd really love to be able to quickly "fix" the order of my = sorted headings by automating a ":sorted:" property.=A0 Another u= se I can imagine for this is when juggling an outline, one could "fix&= quot; an order that reads well, and then play around with it to see how it = might flow better, knowing that it would be easy to return to the last pref= erred sort-order - like a rollback.=A0 During the last few weeks I would ha= ve made use of this not only when working on songs, but also when designing= song programmes and writing my resum=E9.

If a sorted headline got moved to a new parent its sort-order might be = a duplicate one of its siblings, but I don't really see that as a probl= em - the user knows it's "only text" after all.=A0 I don'= t know whether it might be desired to similarly fix the sort-order of 1st l= evel headlines; perhaps the command could act per current file, with a <= to narrow down to the current tree.=A0 I'm also not sure how to deal w= ith larger numbers - 01-99 seems like a good default but could one have an = option for 001-999?=A0 I also wonder about adding the property to more than= one level at a time, but might that be a bit much in terms of affecting pe= rformance?

Does anyone else see this as potentially useful?

Gez
GNU Ema= cs 23.3.1 and org-version 7.7

--0016e6d7e100c7699a04aeb6bdb9--