From mboxrd@z Thu Jan 1 00:00:00 1970 From: filebat Mark Subject: Re: when export org-mode to html, don't export entries of TODO, CANCELED Date: Fri, 18 Nov 2011 10:10:53 +0800 Message-ID: References: <878vnei4nd.fsf@norang.ca> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=e89a8f50282ac505e404b1f8d80d Return-path: Received: from eggs.gnu.org ([140.186.70.92]:39888) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RRDup-0006rU-Ev for emacs-orgmode@gnu.org; Thu, 17 Nov 2011 21:10:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RRDuo-0001bk-6y for emacs-orgmode@gnu.org; Thu, 17 Nov 2011 21:10:55 -0500 Received: from mail-gy0-f169.google.com ([209.85.160.169]:50693) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RRDuo-0001bf-2d for emacs-orgmode@gnu.org; Thu, 17 Nov 2011 21:10:54 -0500 Received: by ghrr17 with SMTP id r17so6995ghr.0 for ; Thu, 17 Nov 2011 18:10:53 -0800 (PST) In-Reply-To: <878vnei4nd.fsf@norang.ca> 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: Bernt Hansen Cc: Denny Zhang , emacs-orgmode@gnu.org --e89a8f50282ac505e404b1f8d80d Content-Type: text/plain; charset=ISO-8859-1 Hi Bernt I am not sure whether I get you correctly. The behavior of [#+OPTIONS: tasks:("DONE") todo:nil] looks like (setq org-export-with-todo-keywords nil). My purpose is not to export entries of "TODO", "CANCELED", etc, instead of only strings of "TODO", "CANCELED". On Fri, Nov 18, 2011 at 9:46 AM, Bernt Hansen wrote: > filebat Mark writes: > > > Exporting org-mode's entries to html is a fantastic way for knowledge > > sharing! > > > > Usually entries of "TODO" "HALF" "DELEGATE" "CANCELED" "DEFERRED" are > > incomplete/immature knowledge. Thus, I don't want to export > > them. Furthermore, after they are marked as "DONE", I'd like to export > > them. > > > > Any idea for how to do this? Note that org-export-exclude-tags > > doesn't help us, at my first glance. > > > > > > Draft solution: > > After checking the implementation of org-mode for this part, I found > > org-export-handle-export-tags function. It determines what to be > > excluded when exporting, by search regexp of :\\(TAG1\\|TAG2\\|...\\): > > in entries' title. > > > > Thus I override org-export-handle-export-tags, by search regexp of > \\(TAG1\\|TAG2\\|...\\) with leading/tailing colon removed. > > > > It's ugly but it works. > > So my open question is what's the better solution? > > Hi, > > Try adding this to your org file and then exporting > > #+OPTIONS: tasks:("DONE") todo:nil > > Regards, > Bernt > -- Thanks & Regards Denny Zhang --e89a8f50282ac505e404b1f8d80d Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Bernt

I am not sure whether I get you correctly.

The b= ehavior of [#+OPTIONS: tasks:("DONE") todo:nil] looks like (setq = org-export-with-todo-keywords nil).

My purpose is not to export entr= ies of "TODO", "CANCELED", etc, instead of only strings= of "TODO", "CANCELED".



On Fri, Nov 18, 2011 at 9:46 AM, Ber= nt Hansen <bernt@no= rang.ca> wrote:
filebat Mark <filebat.mark@gmail.com> writes:

> Exporting org-mode's entries to html is a fantastic way for knowle= dge
> sharing!
>
> Usually entries of "TODO" "HALF" "DELEGATE&qu= ot; "CANCELED" "DEFERRED" are
> incomplete/immature knowledge. =A0Thus, I don't want to export
> them. Furthermore, after they are marked as "DONE", I'd = like to export
> them.
>
> Any idea for how to do this? =A0Note that org-export-exclude-tags
> doesn't help us, at my first glance.
>
>
> Draft solution:
> After checking the implementation of org-mode for this part, I found > org-export-handle-export-tags function. =A0It determines what to be > excluded when exporting, by search regexp of :\\(TAG1\\|TAG2\\|...\\):=
> in entries' title.
>
> Thus I override org-export-handle-export-tags, by search regexp of \\(= TAG1\\|TAG2\\|...\\) with leading/tailing colon removed.
>
> It's ugly but it works.
> So my open question is what's the better solution?

Hi,

Try adding this to your org file and then exporting

#+OPTIONS: tasks:("DONE") todo:nil

Regards,
Bernt



--
Thanks & Regards
Denny Zhang

--e89a8f50282ac505e404b1f8d80d--