From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Using org-mode as day planner Date: Fri, 10 Aug 2012 10:09:12 +0200 Message-ID: <871ujf4193.fsf@gnu.org> References: <5023F648.1060701@jugband.net> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38043) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SzkH0-0008QG-Iq for emacs-orgmode@gnu.org; Fri, 10 Aug 2012 04:08:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SzkGx-00086f-S2 for emacs-orgmode@gnu.org; Fri, 10 Aug 2012 04:08:46 -0400 Received: from mail-wi0-f177.google.com ([209.85.212.177]:39983) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SzkGx-00086b-L5 for emacs-orgmode@gnu.org; Fri, 10 Aug 2012 04:08:43 -0400 Received: by wibhn17 with SMTP id hn17so153075wib.12 for ; Fri, 10 Aug 2012 01:08:42 -0700 (PDT) In-Reply-To: <5023F648.1060701@jugband.net> (Jack Erwin's message of "Thu, 09 Aug 2012 11:41:28 -0600") 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: Jack Erwin Cc: emacs-orgmode@gnu.org Hi Jack, Jack Erwin writes: > So, a couple of questions: > > 1) Is this a sane approach? My elisp is average at best, and the > org-mode devs could probably think of a more graceful way to do this. I don't know. If I were you, I would give Org a little more time before trying to make it behave as planner behaves. Also, you might be interested in org-datetree.el, which helps storing things relatively to a date, which sounds a bit more `à la planner'. http://orgmode.org/w/?p=org-mode.git;a=blob_plain;f=lisp/org-datetree.el;hb=HEAD > 2) Is there a reason that the org-agenda-after-show-hook is only called > when using org-agenda-goto and not org-agenda-switch-to, or is this a > bug? A leftover, fixed now, thanks! -- Bastien