From mboxrd@z Thu Jan 1 00:00:00 1970 From: James TD Smith Subject: Re: RFC: Improvements to org-remember Date: Sun, 30 Nov 2008 02:00:51 +0000 Message-ID: <20081130020051.GG62148@yog-sothoth.mohorovi.cc> References: <20081123232557.GC62148@yog-sothoth.mohorovi.cc> <21E07097-0FF3-40E1-8BD8-A12B7D5099BC@alexanderonline.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L6bcG-0006h0-KJ for emacs-orgmode@gnu.org; Sat, 29 Nov 2008 21:00:56 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L6bcF-0006go-2W for emacs-orgmode@gnu.org; Sat, 29 Nov 2008 21:00:56 -0500 Received: from [199.232.76.173] (port=34967 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L6bcE-0006gl-VR for emacs-orgmode@gnu.org; Sat, 29 Nov 2008 21:00:55 -0500 Received: from 81-86-40-42.dsl.pipex.com ([81.86.40.42]:63752 helo=yog-sothoth.mohorovi.cc) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1L6bcE-0007JY-2C for emacs-orgmode@gnu.org; Sat, 29 Nov 2008 21:00:54 -0500 Received: from yog-sothoth.mohorovi.cc (localhost [127.0.0.1]) by yog-sothoth.mohorovi.cc (8.14.2/8.14.2) with ESMTP id mAU20pJw004153 for ; Sun, 30 Nov 2008 02:00:51 GMT (envelope-from ahktenzero@mohorovi.cc) Received: (from ahktenzero@localhost) by yog-sothoth.mohorovi.cc (8.14.2/8.14.2/Submit) id mAU20pb8004152 for emacs-orgmode@gnu.org; Sun, 30 Nov 2008 02:00:51 GMT (envelope-from ahktenzero@mohorovi.cc) Content-Disposition: inline In-Reply-To: <21E07097-0FF3-40E1-8BD8-A12B7D5099BC@alexanderonline.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi Ben, On 2008-11-24 11:50:53(+0200), Ben Alexander wrote: > On 2008-Nov-24, at 04:25, emacs-orgmode-request@gnu.org wrote: > > ** Automatic sorting > > > Right now, I have a :SORT: property in my property drawer which looks > like: > :SORT: C-c S-6 p > This is just a reminder to me for the key chord I need to play to get > the sort I want. It's conveniently located near the headline and not > too hard to open and read when I need to resort manually. > > It seems to me that having an hook like 'org-remember-after-filing > would allow people to choose what kinds of updating they wanted done > after a remember template was used. Mixing this with different types > of templates may take some care: you don't want to run all the hooks > inside a save-excursion if the point to to allow the hook to move > point to a special place, but then all hooks would have to be written > with that in mind. Perhaps the hooks should be run inside a (let ) > with some official bindings for markers for the following: > - org-remember-marker-to-beginning-of-new-text > - org-remember-marker-to-end-of-new-text > - org-remember-marker-to-parent-headline (perhaps most useful for > non-headline remember templates) > - org-remember-template-type This is basically how I was thinking of implementing the sort after filing (and the other post-commit update functions). > But automatic sorting seems useful in many other contexts (like after > scheduling or rescheduling an item, or changing priority, or editing > the headline text) so perhaps some wishes/ideas from the list would be > appropriate. Could org-mode take ownership of the :SORT: property for > headlines, and have a org-sort-file-using-property (or a org-sort- > headline-using-property) which could be added to hook lists where-ever > the user wanted? I think it would be rather difficult to get automatic sorting working for editing the headline text. Org doesn't have hook lists for priority or scheduling changes either. I do like the idea of defining a default sort for a tree. We would need a :SORT_KEY: property as well, for sorting by property or table column, and a #+SORT: facility for file level sorting. The property could be used to determine a default sort for org-sort, with a new option added to select the default (maybe C-c ^ RET). > Or is this too specific? Would it be nice to have plain lists (or > checkboxed lists) have some kind of sort property too? Where could a > user store this data so it could be easy to see but also easy to ignore. I'm not sure it's necessary to be able to do this in plain lists. If a plain list item has enough activity under it to need sorting on a regular basis its probably worth promoting it to a headline. -- |---|