emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ypo <ypuntot@gmail.com>
To: Jack Kamm <jackkamm@gmail.com>
Cc: Ihor Radchenko <yantar92@posteo.net>, Org-mode <emacs-orgmode@gnu.org>
Subject: Re: org-icalendar export problems
Date: Thu, 1 Feb 2024 20:38:40 +0100	[thread overview]
Message-ID: <3251af4c-d7b1-c765-190b-4b0c8cac92b5@gmail.com> (raw)
In-Reply-To: <87zfwna270.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]

I got org updated, following Ihor's instructions: Org mode version 
9.7-pre (release_N/A-N/A-afc529 @ ./org-9.7pre0.20240130.161905/)

If I were able to fulfill a good process to export from agenda to 
icalendar, maybe we could share an easy process, useful for a lot of 
users that miss a good android calendar visualization. Do you think it 
could be possible to export, in an async way, a calendar file every time 
when a new timestamp, Schedule or Deadline are added to a buffer? What 
would happen if an export process is already running and a new timestamp 
is added? Would it be robust enough or prone to errors? I can see that 
even if a footnote is not correct, the process seems to be interrupted.

Actual state: when I try to export to icalendar, the behavior is quite 

+ [c] Combine all agenda files: I don't get any ics file. I don't know 
what is the problem.

+ [a] All agenda files: I get just an ics file. I thought I would get 
one file for each agenda file.


On 30/01/2024 5:13, Jack Kamm wrote:
> ypuntot<ypuntot@gmail.com>  writes:
>> Problem! Found 1 error
>> Errors
>> Lines not delimited by CRLF sequence near line # 1
>> Reference: RFC 5545 3.1. Content Lines
> Which version of Org are you using? (M-x org-version)
> Org 9.7 (unreleased) contains some fixes for how ox-icalendar handles
> newlines. If you are using a previous version of Org, please try out the
> latest main branch and see if it fixes the problem.

[-- Attachment #2: Type: text/html, Size: 2506 bytes --]

  reply	other threads:[~2024-02-01 19:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 16:17 org-icalendar export problems ypuntot
2024-01-29 16:31 ` Ihor Radchenko
2024-01-30  3:30   ` Jack Kamm
2024-01-30  3:57     ` ypuntot
2024-01-30  4:13       ` Jack Kamm
2024-02-01 19:38         ` Ypo [this message]
2024-02-02 16:53           ` Ihor Radchenko
2024-02-02 21:16             ` [BUG] No result exporting combined org-agenda files to icalendar [9.6.15 (release_9.6.15 @ z:/emacs-i686/share/emacs/29.2/lisp/org/)]. It was: " Ypo
2024-02-02 21:25               ` Ihor Radchenko
2024-02-03 12:13                 ` Ypo
2024-02-03 14:24                   ` Fraga, Eric
2024-02-03 18:58                   ` Jack Kamm

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=3251af4c-d7b1-c765-190b-4b0c8cac92b5@gmail.com \
    --to=ypuntot@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jackkamm@gmail.com \
    --cc=yantar92@posteo.net \


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