emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Guy Wiener <gwiener@cs.bgu.ac.il>
To: Carsten Dominik <carsten.dominik@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: How not to export blocked tasks to iCal?
Date: Sun, 10 May 2009 10:50:17 +0300	[thread overview]
Message-ID: <4A068739.3090502@cs.bgu.ac.il> (raw)
In-Reply-To: <DC7FBC2E-CF56-4462-A25E-358850FCB90E@gmail.com>

I mean VTODO.

I think it would be really great if it is configurable.

If it's not, can you at least point me to the relevant spot in the code 
in which such filtering can be done - Maybe a hook function?


- Guy


Carsten Dominik wrote:

>
> On May 10, 2009, at 9:21 AM, Guy Wiener wrote:
>
>> Thanks to everyone, but before the discussion gets out of hand: Is 
>> there a way not to export blocked tasks to iCal file? Org-mode can 
>> identify blocked tasks, since it can hide them in the agenda view. 
>> Can it be configured not to export them?
>
> No, not currently.
>
> You mean for VTODO, or also for VEVENT?
>
> - Carsten
>
>>
>>
>> Thanks again.
>>
>>
>> Carsten Dominik wrote:
>>
>>> This is, I think, somewhat complex, you'd have to get Thomas Baumann,
>>> author of org-bbdb anniversary support, to write something to
>>> support for this.
>>>
>>> - Carsten
>>>
>>> On May 10, 2009, at 3:54 AM, Richard Riley wrote:
>>>
>>>> Guy Wiener <gwiener@cs.bgu.ac.il> writes:
>>>>
>>>>> Hello everyone,
>>>>> I use orgmode to write down TODO tasks with dependencies (using
>>>>> org-enforce-todo-dependencies). I want to export the tasks to an
>>>>> iCalendar file, but *without* the blocked tasks (i.e, tasks that have
>>>>> unfinished dependencies). The agenda view hides these tasks if you 
>>>>> set
>>>>> org-agenda-dim-blocked-tasks. It there a way to configure the 
>>>>> iCalendar
>>>>> export to ignore these tasks too, like in the agenda view?
>>>>>
>>>>> Thanks,
>>>>> Guy Wiener.
>>>>
>>>> It would be nice if the results from
>>>>
>>>> #+CATEGORY: Anniv
>>>> %%(org-bbdb-anniversaries)
>>>>
>>>> were included too. My initial test indicate they are not.
>>>>
>>>>
>>>> _______________________________________________
>>>> Emacs-orgmode mailing list
>>>> Remember: use `Reply All' to send replies to the list.
>>>> Emacs-orgmode@gnu.org
>>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>
>>>
>>
>>
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Remember: use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

  reply	other threads:[~2009-05-10  7:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07  7:19 How not to export blocked tasks to iCal? Guy Wiener
2009-05-10  1:54 ` Richard Riley
2009-05-10  7:17   ` Carsten Dominik
2009-05-10  7:21     ` Guy Wiener
2009-05-10  7:28       ` Carsten Dominik
2009-05-10  7:50         ` Guy Wiener [this message]
2009-05-10 10:34 ` Carsten Dominik

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=4A068739.3090502@cs.bgu.ac.il \
    --to=gwiener@cs.bgu.ac.il \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.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).