emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Daniel Bausch <bausch@dvs.tu-darmstadt.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: agenda: personal priority for today
Date: Thu, 11 Apr 2013 09:04:39 +0200	[thread overview]
Message-ID: <87d2u1y2d4.fsf@bzg.ath.cx> (raw)
In-Reply-To: <516657E8.90003@dvs.tu-darmstadt.de> (Daniel Bausch's message of "Thu, 11 Apr 2013 08:27:52 +0200")

Hi Daniel,

Daniel Bausch <bausch@dvs.tu-darmstadt.de> 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.


  reply	other threads:[~2013-04-11  7:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10 12:35 agenda: personal priority for today Michael Heinrich
2013-04-10 19:21 ` John Wiegley
2013-04-10 22:58   ` Bastien
2013-04-10 23:17     ` Christopher Allan Webber
2013-04-10 23:32       ` Bastien
2013-04-11  6:27         ` Daniel Bausch
2013-04-11  7:04           ` Bastien [this message]
2013-04-11  7:34             ` Daniel Bausch
2013-04-11  8:37               ` Bastien
2013-04-11  8:40                 ` Bastien
2013-04-11  9:27                 ` Daniel Bausch
2013-04-16 15:58         ` Christopher Allan Webber
2013-04-16 16:30           ` Bastien
2013-04-21 13:31             ` Christopher Allan Webber
2013-04-17  8:44           ` Daniel Clemente
2013-04-18 10:23             ` Bastien
2013-04-18 12:54               ` Daniel Clemente
2013-04-10 19:50 ` Samuel Wales
2013-04-11 12:16 ` Michael Brand

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d2u1y2d4.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=bausch@dvs.tu-darmstadt.de \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).