Re: [O] agenda: personal priority for today

[Daniel Bausch]

Hi Bastien,

Am 11.04.2013 09:04, schrieb Bastien:
> Hi Daniel,
> 
> Daniel Bausch <address@hidden> 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.

Just do not touch the IDs of items not currently visible or add the name
of the agenda to which this applies and have an AGENDA_BEFORE per agenda.

> 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.

Then maybe a 31st is required ;-)

I already use some of those 30 strategies, but am also not 100%
satisfied with the result.  Global priorities are somewhat hard to
define.  It is mentally easier to just say, hey this is more important
than that.  The sequence in the Org file can reflect the order of
insertion or the typical order of processing within a tree of projects.
 But when steps from different projects mix within one daily agenda, it
is not always possible to prioritize project A over project B.
Repeatedly exchanging project A and project B in the file is cumbersome
and if there are two projects from different files, one would need to
adjust the org-agenda-files variable.

I often have more TODOs on the daily agenda, than I will be able to
resolve on that day.  Deciding on the next most important one everytime
when switching the task makes me tired.  Doing things in a random order
feels dangerous.

How do you decide what to do next?

Regards,
Daniel Bausch

-- 
Daniel Bausch
Wissenschaftlicher Mitarbeiter
Technische Universität Darmstadt
Fachbereich Informatik
Fachgebiet Datenbanken und Verteilte Systeme

Hochschulstraße 10
64289 Darmstadt
Germany

Tel.: +49 6151 16 6706
Fax:  +49 6151 16 6229