emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.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 10:37:05 +0200	[thread overview]
Message-ID: <87li8pv4y6.fsf@bzg.ath.cx> (raw)
In-Reply-To: <51666798.7040107@dvs.tu-darmstadt.de> (Daniel Bausch's message of "Thu, 11 Apr 2013 09:34:48 +0200")

Hi Daniel,

Daniel Bausch <bausch@dvs.tu-darmstadt.de> writes:

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

Mhh... looks like overengineering to me.

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

I bind `=' to a custom agenda command that will find out what to do
next depending on the Emacs context.

For example, when reading emails, C-c a = will find next emails to
process; when in *.el C-c a = will find next Emacs/Org bugs to deal
with; when in my big garden.org file, C-c a = will find the next
useless stuff I want to watch/read. 

(See `org-agenda-custom-commands-contexts' if you don't use it yet.)

I don't use clocking that much, but I do set efforts nonetheless,
because I like using `org-agenda-max-effort' in agenda views: this
way I'm sure the agenda is not cluttered with tasks I didn't care
enough about to set an effort for them.

And above all, I try to discipline myself not setting to many
"NEXT" tasks.  First my notion of "NEXT" was "Yeah, I can do this
quickly!", now it is more like "This *needs* to be done next",
obviously a small set.

So as you see, I don't need too much fancy sorting in the agenda
because I try to keep my agenda very short.  The need for fancy
sorting tells that agendas are too big, and sorting will only
help, not solve this problem.

2 cents of course,


  reply	other threads:[~2013-04-11  8:37 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
2013-04-11  7:34             ` Daniel Bausch
2013-04-11  8:37               ` Bastien [this message]
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=87li8pv4y6.fsf@bzg.ath.cx \
    --to=bzg@gnu.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).