From: Ihor Radchenko <yantar92@posteo.net>
To: Ypo <ypuntot@gmail.com>
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: Fri, 02 Feb 2024 21:25:14 +0000 [thread overview]
Message-ID: <87jznmsgn9.fsf@localhost> (raw)
In-Reply-To: <532da0f8-b93e-6e21-8ea4-0046808585ed@gmail.com>
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.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-02-02 21:22 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 [this message]
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jznmsgn9.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jackkamm@gmail.com \
--cc=ypuntot@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.