From: Ypo <ypuntot@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Jack Kamm <jackkamm@gmail.com>, Org-mode <emacs-orgmode@gnu.org>
Subject: Re: [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: org-icalendar export problems
Date: Sat, 3 Feb 2024 13:13:12 +0100 [thread overview]
Message-ID: <48883dc2-bf58-ba5c-8790-449384ef9c40@gmail.com> (raw)
In-Reply-To: <87jznmsgn9.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
Thanks, Ihor
I can't share my private org files. And I find myself unable to isolate
the causes of the possible errors.
I think I will keep waiting till somebody shares an easy and robust way
to get an .ics calendar from org files.
Best!
On 02/02/2024 22:25, Ihor Radchenko wrote:
> Ypo<ypuntot@gmail.com> writes:
>
>> I am sharing a bug report from emacs -q. I don't know how to use a
>> different org-version that the built-in (or if I should).
> Sorry for not being clear. Let me elaborate what I expect.
>
> 1. Create example Org file or a set of Org files, open them with
> emacs -Q, and try to trigger the problem where you expect to see ics
> file, but it does not appear
>
> 2. If you can do it, share the example Org files and each step you
> performed after emacs -Q until you encountered the problem.
>
> The idea is providing me with enough info to re-create the problem on my
> computer, so that I can investigate in depth.
>
[-- Attachment #2: Type: text/html, Size: 1787 bytes --]
next prev parent reply other threads:[~2024-02-03 12:14 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
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 [this message]
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:
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=48883dc2-bf58-ba5c-8790-449384ef9c40@gmail.com \
--to=ypuntot@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jackkamm@gmail.com \
--cc=yantar92@posteo.net \
/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).