emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: How could I mix COMMENT and TODO?
Date: Thu, 05 Apr 2012 13:55:09 +0200	[thread overview]
Message-ID: <804nsyjsv6.fsf@somewhere.org> (raw)
In-Reply-To: 8662demmxr.fsf@iro.umontreal.ca

Hi François,

François Pinard wrote:
> Hi, Orgers of this world! :-)
>
> I do not find how to mix COMMENT and TODO in a working way, and I
> thought that someone could advise me.
>
> For ease and simplicity, I try to keep everything related to some topic
> in a single file, merely commenting (C-c ;) headers for those parts I do
> not want to publish.
>
> I would also like to keep my TODO entries for this topic in the same
> file, and these are usually not to be published either.  However, TODO
> seems to be ignored whenever it is on or under a COMMENT header.  When I
> comment a TODO entry, the TODO gets un-highlighted, and the entry
> scheduling disappears from the agenda.
>
> So, until I find something better, I keep these TODO in another file,
> which I find an awkward compromise.  I could use #+BEGIN_COMMENT and
> such within the entry, but the header itself gets published, which I do
> not want.  So, what is the proper way for fully preventing a working
> TODO header from being published?  Or else, what is the good approach?

Instead of COMMENT'ing entries, I prefer the "tag" version of the same
functionality: mark the entries you don't wanna see exported with the
`noexport' tag.

Best regards,
  Seb

-- 
Sebastien Vauban

  reply	other threads:[~2012-04-05 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-05 11:34 How could I mix COMMENT and TODO? François Pinard
2012-04-05 11:55 ` Sebastien Vauban [this message]
2012-04-05 22:44 ` suvayu ali
2012-04-06  1:26   ` François Pinard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=804nsyjsv6.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).