On Thu, Aug 30 2012, Bastien wrote:
> Hi,
>
> Charles Philip Chan writes:
>
>> I do have an Agenda buffer opened when I tested it out. I can reproduce
>> what you got with no Agenda buffer present.
>
> This is because the function calls `org-compile-prefix-format', which
> needs an agenda buffer.
On Thu, Aug 30 2012, Charles Philip Chan wrote:
> Michal Sojka writes:
>
> Hi Nichal:
>
>> Does anybody have the same problem or better a fix for it?
>>
>> Org-mode version 7.8.11, I've tried that with both emacs 23 and 24.
>
> Works fine here with the lat
Hello all,
I've just discovered calfw[1]. When I try it to display my Org schedule
with cfw:open-org-calendar, it fails when executing
(org-compile-prefix-format nil), because it cannot open agenda buffer.
So I put (org-prepare-agenda "calfw-org") in front of that command,
which makes it not to fa
* org-icalendar.el (org-print-icalendar-entries): Make alarm duration
RFC5545 compliant.
The format of alarm trigger was incorrect because "T" letter from
dur-time element was missing (see
http://tools.ietf.org/html/rfc5545#section-3.3.6). This caused some
software (such as KOrganizer) to not inte
Hi all,
I wanted to try the experimental Mediawiki exporter and it fails to
export documents with dot code blocks (as the one provided below). I
tried to fix that myself but my elisp and org-babel knowledge is not
sufficient for that. I used org-mode 7.7.
The error was: "file-name-extension: Wron
ssage containing the patch:
>
> > Content-Type: text/plain; charset="utf-8"
> > MIME-Version: 1.0
> > Content-Transfer-Encoding: 7bit
> > Subject: [O] icalendar: Make alarm duration RFC5545 compliant
> > Date: Thu, 12 May 2011 13:30:19 -
> > From:
The format of alarm trigger was incorrect because "T" letter from
dur-time element was missing (see
http://tools.ietf.org/html/rfc5545#section-3.3.6). This caused some
software (such as KOrganizer) to not interpret the alarms correctly.
---
lisp/org-icalendar.el |2 +-
1 files changed, 1 inser
