From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: GTD: Solving the bottleneck of converting incoming mails to NEXT actions Date: Tue, 25 Sep 2007 18:29:54 +0200 Message-ID: <87myvad7y5.fsf@bzg.ath.cx> References: <87myva7vqb.fsf@bzg.ath.cx> <87k5qeoild.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IaDIQ-0003VH-UJ for emacs-orgmode@gnu.org; Tue, 25 Sep 2007 12:30:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IaDIP-0003Ua-BD for emacs-orgmode@gnu.org; Tue, 25 Sep 2007 12:30:02 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IaDIO-0003UH-UF for emacs-orgmode@gnu.org; Tue, 25 Sep 2007 12:30:00 -0400 Received: from hu-out-0506.google.com ([72.14.214.237]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IaDIO-0006W1-DS for emacs-orgmode@gnu.org; Tue, 25 Sep 2007 12:30:00 -0400 Received: by hu-out-0506.google.com with SMTP id 23so1072335huc for ; Tue, 25 Sep 2007 09:29:59 -0700 (PDT) In-Reply-To: (Georg C. F. Greve's message of "Tue, 25 Sep 2007 18:08:17 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org "Georg C. F. Greve" writes: > and when making "~/Tools/Org/E.org" the default file name, things seem > to work fine with the one exception that instead of creating the heading > that was specified as default, it creates a "* Notes" heading. I cannot reproduce this. Anyway, since the headings defined in the templates are created once, you can create them by hand for now then leave the rest of the config untouched. > If a heading is created, why not creat the default? It's what Org does for me. > On changing the file names, I wanted to avoid that, because the file > names are used in generating the agenda, and I don't want to lose four > characters in the compact view. The agenda display also uses the #+CATEGORY property. So that you can have long-filenames-are-fun.org, if the category for this file is LFNAF then the agenda will show LFNAF :) > "Georg's Email TODO Org File -*- mode: org; -*-" Agreed! > So I consider that necessity a bug. The user has explicitly specified > that this is an Org file, remember should not consider itself smarter > than the user and insist on the file name extension. Did you try to remember a note with "~/Tools/Org/E" and the string "-*- mode: org; -*-"? The test is done with (org-mode-p), so the string on the first line should be okay. > b) remove file name extension sensitivity for Org mode files, or make > it smart enough to *actually* read the buffer to see what mode it is > in, because it should have to open the file to add the item. This is currently the case. -- Bastien