[O] Bernt Hansen's setup for recent orgmode versions
Hi, Is anybody aware of an adaptation of Bernt Hansen's orgmode setup for the current orgmode version? His setup is for 8.x... Thanks Markus
Re: [O] Bernt Hansen's
Sebastien Vauban writes: > rene wrote: > > > I find his code pretty close to what GTD should look like. There are a few > > things though that could be twicked a bit in order to comply with David > > Allen's new book on Getting Things Done. > > Can you detail them, for our own information, please? Here are a few thoughts. Feel free to provide feedback and enhancements. Associating what GTD calls "Areas of Responsibility" to orgmode categories is great. But launching a search for these categories (areas of responsibility) has to be hardcoded in everyone's config file. It would be great if this could work like for Tags (C-a a M) or Todo keywords (C-a a T). Why not have a "C-a a R" which would prompt us for our own various Areas of Responsibility. Of course there is an org-agenda-filter-by-category function but this function should then work more as org-agenda-filter-by-tag where the category would either be selected with a fast selection letter or when you hit the TAB key you're being prompted for a list of possible categories. Within GTD, the way you are to choose which task to perform never relies on a preset priority level but on three limiting criteria, namely - your context: What can I do where I am? - your time available: How much time do I have? - your energy: How much energy do I have It's easy to implement your context as Tags: @home, @computer, @office, @internet, @errands, etc. It's therefore easy to extract/filter tasks pertaining to a particular context using "C-a a M". I find the org-effort-property misleading. It looks like you're talking about the energy criteria but in fact this deals with the estimated time duration of a task. Could one straighten this up? The estimated "task-duration" could then replace the misleading "org-effort" property. The "energy" level should work as the org-priority. "A" could mean the task will require from me a high level of priority, whereas "C" could mean a low level of priority. In David Allen's new book, which should be available early 2015, the three basic steps for the GTD method are: Capture, Clarify and Organize. In terms of vocabulary, he's not talking about a "task to refile" but rather an "action to clarify and organize", which in orgmode would consist in assigning the right: context (tag), duration, energy, project, where a project would pertain to a area of responsibility (category). For me this notion of projects (and sub-projects, sub-sub-projects, etc.) in org-mode is not that easy to deal with. Maybe I need to investigate things a bit more. Any idea would be welcome. Since the Weekly Review is such a key part in the GTD methodology, I don't think there's any real need to differentiate between active vs stuck projects. Every 7 to 10 days, you will go over your projects and thus identify the ones that need a next action to be defined. The ones that are considered as DONE, if all their sub-actions and sub projects are themselves done or canceled. -- rene
Re: [O] Bernt Hansen's
rene writes: > I wonder whether Bernt would agree to turn his config file into an actual > lisp package that could be available via Elpa? > > I find his code pretty close to what GTD should look like. There are a few > things though that could be twicked a bit in order to comply with David > Allen's new book on Getting Things Done. > > I will try to contact Bernt and ask him to deliver such an org-gtd.el > package. That would be great for the orgmode community. Hi Rene, I don't have time to maintain an Elpa package of this stuff currently. This past Friday I just did a 'catch up' in gnus on this mailing list and skipped 8600+ unread articles (including this one) due to lack of available time. Thanks for the email in private that brought this thread to my attention. It should be possible to extract the lisp from my document (http://doc.norang.ca/org-mode.org) and generate a lisp file with C-c C-v C-t. This is described at the end of http://doc.norang.ca/org-mode#HowToUseThisDocument >From there you can edit whatever you need to for your settings. I personally don't want to conform strictly to David Allen's idea of how GTD should work. I like to roll-my-own way of doing things and if an Elpa packaging of this code would require learning and modifying the workflows to match David Allen's latest book I simply don't have time for that undertaking. Someone else is welcome to take that on if they are interested. I just discovered late last week that one of my settings relies on a feature of the org-mode master branch (and has for over a year) and this change has not been included in any maintenance release of org-mode. Lots of people have contacted me about the breaking signature change in org-remove-drawer-at which is posted in my config since I use the master branch of org-mode. I think most people will be using official released versions of org-mode so I'm not sure how best to handle this issue until Org 8.3 is released which is supposed to include this signature change. I will probably just document the signature change and provide alternative code to use in the extracted version for maintenance releases until 8.3 is created. Best Regards, Bernt
Re: [O] Bernt Hansen's
Sebastien Vauban writes: > Hello Rene, > > rene wrote: >>> Indeed - Bernt's writeup has been the source of inspiration for lots of >>> people on this list. > > For sure. > >> I find his code pretty close to what GTD should look like. There are a few >> things though that could be twicked a bit in order to comply with David >> Allen's new book on Getting Things Done. > > Can you detail them, for our own information, please? > > Best regards, > Seb I'd like to see these as well, please! Dave
Re: [O] Bernt Hansen's
Hello Rene, rene wrote: >> Indeed - Bernt's writeup has been the source of inspiration for lots of >> people on this list. For sure. > I find his code pretty close to what GTD should look like. There are a few > things though that could be twicked a bit in order to comply with David > Allen's new book on Getting Things Done. Can you detail them, for our own information, please? Best regards, Seb -- Sebastien Vauban
[O] Bernt Hansen's
Nick Dokos gmail.com> writes: > > Gary Oberbrunner oberbrunner.com> writes: > > > Thomas S. Dye tsdye.com> wrote: > > > > > One solution is to use a capture template for TODO items and then > > > refile them. I picked this up from Bernt Hansen and like it a lot: > > > http://doc.norang.ca/org-mode.html#Capture > > > > Wow, that guy is serious! I don't think his setup solves what I'm > > looking for, but there is so much great stuff in there it'll take me > > weeks to check it all out. > > Indeed - Bernt's writeup has been the source of inspiration for lots of > people on this list. I wonder whether Bernt would agree to turn his config file into an actual lisp package that could be available via Elpa? I find his code pretty close to what GTD should look like. There are a few things though that could be twicked a bit in order to comply with David Allen's new book on Getting Things Done. I will try to contact Bernt and ask him to deliver such an org-gtd.el package. That would be great for the orgmode community. --