From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: agenda: personal priority for today Date: Thu, 11 Apr 2013 09:04:39 +0200 Message-ID: <87d2u1y2d4.fsf@bzg.ath.cx> References: <51655C8A.4070806@haas-heinrich.de> <87mwt60z8j.fsf@bzg.ath.cx> <87li8qnfgb.fsf@earlgrey.lan> <87hajeyn9y.fsf@bzg.ath.cx> <516657E8.90003@dvs.tu-darmstadt.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:43074) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UQBYm-0003vS-KS for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 03:04:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UQBYl-0001e2-3G for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 03:04:40 -0400 Received: from mail-wi0-x231.google.com ([2a00:1450:400c:c05::231]:42427) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UQBYk-0001dq-U6 for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 03:04:39 -0400 Received: by mail-wi0-f177.google.com with SMTP id hm14so209636wib.10 for ; Thu, 11 Apr 2013 00:04:38 -0700 (PDT) In-Reply-To: <516657E8.90003@dvs.tu-darmstadt.de> (Daniel Bausch's message of "Thu, 11 Apr 2013 08:27:52 +0200") 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: Daniel Bausch Cc: emacs-orgmode@gnu.org Hi Daniel, Daniel Bausch writes: > I have got another idea: all we need for sorting (from a technical POV) > is a partial order. Why not store exactly that as a property? Assume > every TODO entry has an ID (if it has none and it is required to store > the order, just create one automatically). Then if an entry on the > agenda is reordered, store in a property (e.g. AGENDA_BEFORE), the IDs > of the items that should be sorted after the moved item. To keep things > minimal, maybe store only those IDs, which are absolutely required to > enforce the desired position. But for an easy and effective > implementation, it is also feasible to store all IDs of the currently > visible items that should sort after the moved item. Maybe the IDs need > to be prefixed with a filename or better a file ID so it works on > different machines with different directory layout. Otherwise the IDs > would need to be globally unique (which is not bad by its own, when > items may move between files.) Yes, I see the idea. But one Org headline can be part of several agendas, so an AGENDA_BEFORE property will not work globally. I think we should start thinking from the existing functionalities we have with `org-agenda-sorting-strategy', which is already quite rich (30 strategies!) and flexible. But I cannot think of something that would match the OP request at the moment. -- Bastien