From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Bausch Subject: Re: agenda: personal priority for today Date: Thu, 11 Apr 2013 11:27:20 +0200 Message-ID: <516681F8.3040704@dvs.tu-darmstadt.de> 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> <87d2u1y2d4.fsf@bzg.ath.cx> <51666798.7040107@dvs.tu-darmstadt.de> <87li8pv4y6.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:54011) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UQDme-0000FO-2N for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 05:27:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UQDma-00075h-UI for emacs-orgmode@gnu.org; Thu, 11 Apr 2013 05:27:07 -0400 In-Reply-To: <87li8pv4y6.fsf@bzg.ath.cx> 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: Bastien Cc: emacs-orgmode@gnu.org Hi, Bastien writes: >> How do you decide what to do next? >=20 > I bind `=3D' to a custom agenda command that will find out what to do > next depending on the Emacs context. >=20 > For example, when reading emails, C-c a =3D will find next emails to > process; when in *.el C-c a =3D will find next Emacs/Org bugs to deal > with; when in my big garden.org file, C-c a =3D will find the next > useless stuff I want to watch/read.=20 >=20 > (See `org-agenda-custom-commands-contexts' if you don't use it yet.) >=20 > 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. That sounds interesting. > 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. I currently use the following agenda, which I have always visible on a second monitor together with my single org file in a split view. (setq org-agenda-custom-commands '(("g" "My GTD Agenda" ((agenda "" ((org-agenda-ndays 1) (org-agenda-start-on-weekday nil) (org-agenda-entry-types '(:timestamp :sexp)) (org-agenda-overriding-header "Appointments"))) (agenda "" ((org-agenda-ndays 1) (org-agenda-start-on-weekday nil) (org-agenda-entry-types '(:deadline)) (org-agenda-overriding-header "Upcoming Deadlines") (org-agenda-sorting-strategy '(priority-down time-down)) (org-agenda-skip-function '(org-agenda-skip-entry-if 'todo 'done)))) (agenda "" ((org-agenda-ndays 1) (org-agenda-start-on-weekday nil) (org-agenda-entry-types '(:scheduled)) (org-agenda-overriding-header "Scheduled") (org-agenda-sorting-strategy '(priority-down time-down)) (org-agenda-skip-function '(org-agenda-skip-entry-if 'todo 'done)))) (todo "WAIT" ((org-agenda-sorting-strategy '(priority-down)) (org-agenda-overriding-header "Waiting For"))) (todo "NEXT" ((org-agenda-sorting-strategy '(priority-down effort-down)) (org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled 'deadline)) (org-agenda-overriding-header "Next actions not being scheduled nor having a deadline"))) (todo "TODO" ((org-agenda-sorting-strategy '(priority-down effort-down)) (org-agenda-skip-function '(org-agenda-skip-entry-if 'scheduled 'deadline)) (org-agenda-overriding-header "Future actions not being scheduled nor having a deadline"))) (todo "PROJ" ((org-agenda-overriding-header "Active Projects"))))))) Everything that consists of two or more sub-tasks is marked as a project (PROJ) until it is DONE. A NEXT action is an action that could be done immediately, i.e. there are no other actions that need to be done for being able to do that. In GTD speech a loose end. If a task is just marked with TODO, then there is one or more task that needs to be done, before I will be able to do it. So I end up with a lot of open NEXT and TODO tasks. To select some to be done on a specific day (e.g. today) I use scheduling and deadlines. Sometimes I use efforts, but clocking I use consequently. Project review is supported by using '(org-enforce-todo-dependencies t). So projects with no defined next action are colored differently. Sometimes I go through my big list of open tasks and close some which I am not going to do anymore by setting them to a special done state CNCL. Even if I have only six tasks on my scheduled list for today, knowing that I will not be able to finish all of them really today, I see me constantly judging one against the others trying to find the most important. This eats mental resources, that would be better used doing one of them, but doing simply a random task, keeps me reconsidering, what also eats up mental resources. Has anyone an idea how to escape from that mental state of constant reconsidering? Daniel --=20 Daniel Bausch Wissenschaftlicher Mitarbeiter Technische Universit=E4t Darmstadt Fachbereich Informatik Fachgebiet Datenbanken und Verteilte Systeme Hochschulstra=DFe 10 64289 Darmstadt Germany Tel.: +49 6151 16 6706 Fax: +49 6151 16 6229