From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bernt Hansen Subject: New Exporter BUG/Change in behaviour Date: Fri, 05 Apr 2013 12:52:39 -0400 Message-ID: <87ppy8yl60.fsf@norang.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([208.118.235.92]:48705) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UO9sb-0006MB-PE for emacs-orgmode@gnu.org; Fri, 05 Apr 2013 12:52:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UO9sY-0003yV-ED for emacs-orgmode@gnu.org; Fri, 05 Apr 2013 12:52:45 -0400 Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:15548) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UO9sY-0003yO-AK for emacs-orgmode@gnu.org; Fri, 05 Apr 2013 12:52:42 -0400 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org Hi Nicolas, I finally updated to the latest master branch at work yesterday to move to the new exporter and found the following change I don't know how to deal with. My org file has #+OPTIONS: tasks:todo This globally skips DONE tasks in my exports when I export the entire file in both the old and new exporter. If I select a task with C-c @ that is DONE (or any done state) and try to export that in the new exporter I get nothing (except an empty table of contents) -- even if the Org buffer is narrowed to only that task. The old exporter would export this anyway but it seems the new exporter is honouring the global #+OPTIONS: task:todo even when it is outside the currently narrowed buffer range. There is no local property that I am aware of to say export all todo states. I have to list them individually which isn't user-friendly so I can't reverse the global setting with a local property in my task/subtree. Having to add a property for my exports for email just to get it to override global options really isn't user-friendly since the options per file are different and the user has to know exactly what to undo (and future changes to the global options makes this a moving target) Is this a bug? My current workaround is to delete the global #+OPTIONS line (but that doesn't feel right since I have to add it back to export what is left to do for the entire file when sharing it with others). I regularly export small subtrees (with C-c @) to copy ASCII / HTML export results to emails so the old exporter behaviour was much more predictable in the results I would get when using C-c @. So far the move to the next exporter has been very easy. Great job! Regards, Bernt