From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp2.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id eH1gJ33zu2XIVgEAe85BDQ:P1 (envelope-from ) for ; Thu, 01 Feb 2024 20:39:41 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp2.migadu.com with LMTPS id eH1gJ33zu2XIVgEAe85BDQ (envelope-from ) for ; Thu, 01 Feb 2024 20:39:41 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=YVmDREWd; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1706816381; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=4bmyrthY4md5Cp4LZB/esOz384kGmKWfq/YjIUqhuPI=; b=fQBT4NQ5zDaSUmgyDzbJN8RCcRWWOjZVJPi0memcmi2Bq4s86lzGLdIi9D1vdv3YEn3DKH 1aOwHbYCV9yQ4RLTpiW34bn67JQ8ieusMzo/CYhwpTUnp187fIqjSSEQox/ADnIjEdqAez wmdH5z66zosHqusXxBDK5nF1vhuPJQsI6px5ItD+NB7Yeb2ECMcDLr0QYIDWWbuiombO8n zyEessTSQzUsx8XLQIqgypQVKwtVtYf+cOlLit7wATY3Xe0BTKz8I6owY2SFBKVwcLYUUi gJPdYRtiyk8r6KyGA/2nVBGRFz+gz9qV9+yhoMBkvZZ9IBcXYjneps9m0wprnA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20230601 header.b=YVmDREWd; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=key1; d=yhetil.org; t=1706816381; a=rsa-sha256; cv=none; b=P2+Rmz7wfycIQKnjmgrR+wKBKoAMfUl0B5xcNaRWDWcfTvPMKOARj/mRJ4CKY7bmkytR70 +dm9TDanrH5jqPYar1sFnkztLWahDsEtWOsIVXs5JD9uUwPkMcAGFMH9SH/psO1I+JFN4P gANRf+8XBAp+Fw0xqw8otm7RMgjGCnEX/JwpxVNUVy8UvQ3oQ2wAdNK3fVuOTtiQ/ke/kp 8SWpMeEeCpgAdPhqaSLzNE7UcaIaeZ4H6OBTqIq3KHfnlXzzg72wkoXBfwWrpcKHglp/yh 6sZub0upxUYlLLJg9RaBitKl4VW+9hWODAPKB5MY+MkkSBm+2X/WbDD30uO4BQ== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 5423069053 for ; Thu, 1 Feb 2024 20:39:41 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rVctg-0006XV-3s; Thu, 01 Feb 2024 14:38:52 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rVctc-0006Qg-0N for emacs-orgmode@gnu.org; Thu, 01 Feb 2024 14:38:48 -0500 Received: from mail-wm1-x32d.google.com ([2a00:1450:4864:20::32d]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rVctZ-00076w-5d for emacs-orgmode@gnu.org; Thu, 01 Feb 2024 14:38:46 -0500 Received: by mail-wm1-x32d.google.com with SMTP id 5b1f17b1804b1-40e80046246so205555e9.1 for ; Thu, 01 Feb 2024 11:38:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706816323; x=1707421123; darn=gnu.org; h=in-reply-to:content-language:references:cc:to:subject:from :user-agent:mime-version:date:message-id:from:to:cc:subject:date :message-id:reply-to; bh=4bmyrthY4md5Cp4LZB/esOz384kGmKWfq/YjIUqhuPI=; b=YVmDREWdfy1pYoDlaRbe/c2hjZF4s+g4eHeAMUweVHQnuEYGHXi4TNIJfdhRs3qcim zuaFQSEqbLAUJP73XvlMeswOipiGqNDwf0w95Hih4/3PE8N7ZGtYwe4mCup2lQ85/jdi AEnR1RJxnyo9nW16xeWYu9tbowHyPFJKhIkyauRRpnU7eHX+Mm/nk4hTLwi2jBOtUIWW wFaRBYjwARufsbEJgmvws+oD5JxvbEhWBTE6lCWXrQz6gdu+IQf3zZVQU020iOis7N+r chTf/MldaTYRZLUIJcXlUeWmjmGD5/Cp8SbfAZya7o8XIr8GBUmaHSzhn0rXCZypV4U8 3z5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706816323; x=1707421123; h=in-reply-to:content-language:references:cc:to:subject:from :user-agent:mime-version:date:message-id:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=4bmyrthY4md5Cp4LZB/esOz384kGmKWfq/YjIUqhuPI=; b=PtQfZEnHVkdJIM6oO0maa+0pr8pMt5k7gbQlG++DNCNrAOUqO7z+yucV4Xw1WqGAdN 2YmNdQAKry06QqQs6OOfhkVaLy9PZV7z365Gn9nNX4i+iG4nzHHll/itmlISu7SJQBw9 HBrLlLMzRacxuLpaGizNtxSm8Hr85wgF/TgBFKbvLY31hHjbH6gNSnTVnY9P6xF5kg4P XFjn6T48PIokBnb4rpPSBaaAqKZykRZn04wPiyQEOIFD18uVg0kHwRocQjiVy0kU4OOH 3EaG7GOZzFCNkX+MLdXjbHhv00Uld97Tc41tpnHyTSt5gkLoFehioEYUOUbBS8+Q+Gy1 no/Q== X-Gm-Message-State: AOJu0YxkWIEi3Sfxm3cavusAogmAL5xW1Bisyg1nsUcVBz6Ig64DkcV4 OrTFi2/feXkcnZxtG3UcD2N/o/Az+RhQPCjWhvU6NjzsRaMVnOXT X-Google-Smtp-Source: AGHT+IGXmlWMrrGeTzYYSBB+xhJsQ1i6Ri5EhVzywWxRR/6rcJT8icBk4OECcI5/drWIyNNQCIZSOA== X-Received: by 2002:a05:600c:190a:b0:40e:70f5:a9a3 with SMTP id j10-20020a05600c190a00b0040e70f5a9a3mr8007wmq.5.1706816322941; Thu, 01 Feb 2024 11:38:42 -0800 (PST) X-Forwarded-Encrypted: i=0; AJvYcCVf2F7K8cjbKcJS7RCgjMn2n2mQxgdoR3LH7QJ6K8b0PqzFnWEiHKJZSiz7BLMDy6qprd9v2GpYmd65LpD7Dz4N+1rubsQ= Received: from [192.168.0.97] (static-25-34-227-77.ipcom.comunitel.net. [77.227.34.25]) by smtp.gmail.com with ESMTPSA id r19-20020a05600c35d300b0040e88d1422esm415972wmq.31.2024.02.01.11.38.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 01 Feb 2024 11:38:42 -0800 (PST) Content-Type: multipart/alternative; boundary="------------Vc9afHUlxm2XC3EhAd8KRfEv" Message-ID: <3251af4c-d7b1-c765-190b-4b0c8cac92b5@gmail.com> Date: Thu, 1 Feb 2024 20:38:40 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 From: Ypo Subject: Re: org-icalendar export problems To: Jack Kamm Cc: Ihor Radchenko , Org-mode References: <87jzns3xva.fsf@localhost> <87v87b8pmn.fsf@gmail.com> <55a8d2cd-0eba-4143-84c8-f74bc17ff053@gmail.com> <87zfwna270.fsf@gmail.com> Content-Language: en-GB In-Reply-To: <87zfwna270.fsf@gmail.com> Received-SPF: pass client-ip=2a00:1450:4864:20::32d; envelope-from=ypuntot@gmail.com; helo=mail-wm1-x32d.google.com X-Spam_score_int: -41 X-Spam_score: -4.2 X-Spam_bar: ---- X-Spam_report: (-4.2 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-2.112, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -6.25 X-Migadu-Queue-Id: 5423069053 X-Spam-Score: -6.25 X-Migadu-Scanner: mx11.migadu.com X-TUID: cqJFZsTlpBK8 This is a multi-part message in MIME format. --------------Vc9afHUlxm2XC3EhAd8KRfEv Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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 confusing: + [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. Best! On 30/01/2024 5:13, Jack Kamm wrote: > ypuntot 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. --------------Vc9afHUlxm2XC3EhAd8KRfEv Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

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 confusing:

+ [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. 

Best!

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