emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Friedrich Delgado <friedel@nomaden.org>
To: Bastien <bzg@altern.org>, emacs-orgmode@gnu.org, 668496@bugs.debian.org
Subject: Re: Bug: icalendar export skips todos with a scheduled time-range [7.8.11]
Date: Fri, 24 Aug 2012 16:16:02 +0200	[thread overview]
Message-ID: <20120824141602.GA23984@pre-sense.de> (raw)
In-Reply-To: <20120820111348.GA23549@pre-sense.de>

This is now also fixed, thanks!

Friedrich Delgado schrieb:
> However: If I (setq org-icalendar-use-plain-timestamp nil) as in my
> customisation, scheduled date-ranges are not exported at all (no
> matter what org-icalendar-use-scheduled is set to).
> ( 49905a566970541de76b6d49004c62e50c625a98 from this morning)

        Friedrich Delgado <friedel@nomaden.org>
                             TauPan on Ircnet and Freenode ;)

      parent reply	other threads:[~2012-08-24 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17 12:36 Bug: icalendar export skips todos with a scheduled time-range [7.8.11] Friedrich Delgado
2012-08-19  6:09 ` Bastien
2012-08-19  6:15 ` Bastien
2012-08-20  9:21   ` Friedrich Delgado
2012-08-20 11:13     ` Friedrich Delgado
2012-08-22  0:41       ` Bastien
2012-08-24 14:16       ` Friedrich Delgado [this message]

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:

  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=20120824141602.GA23984@pre-sense.de \
    --to=friedel@nomaden.org \
    --cc=668496@bugs.debian.org \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \


* 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


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).