emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ypo <ypuntot@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Jack Kamm <jackkamm@gmail.com>, Org-mode <emacs-orgmode@gnu.org>
Subject: [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, 2 Feb 2024 22:16:05 +0100	[thread overview]
Message-ID: <532da0f8-b93e-6e21-8ea4-0046808585ed@gmail.com> (raw)
In-Reply-To: <877cjmu7sq.fsf@localhost>

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

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

Emacs  : GNU Emacs 29.2 (build 2, x86_64-w64-mingw32)
  of 2024-01-18
Package: Org mode version 9.6.15 (release_9.6.15 @ 

current state:
  org-link-elisp-confirm-function 'yes-or-no-p
  org-bibtex-headline-format-function #[257 "\300\x01\236A\207" [:title] 3 
"\n\n(fn ENTRY)"]
  org-persist-after-read-hook '(org-element--cache-persist-after-read)
  org-export-before-parsing-hook '(org-attach-expand-links)
  org-cycle-tab-first-hook '(org-babel-hide-result-toggle-maybe 
  org-archive-hook '(org-attach-archive-delete-maybe)
  org-ascii-format-drawer-function #[771 "\x01\207" [] 4 "\n\n(fn NAME 
  org-cycle-hook '(org-cycle-hide-archived-subtrees 
  org-export-with-broken-links 'mark
  org-export-with-clocks t
  org-persist-before-read-hook '(org-element--cache-persist-before-read)
  org-export-default-language "es"
  org-mode-hook '(#[0 "\300\301\302\303\304$\207"
            [add-hook change-major-mode-hook org-fold-show-all append 
local] 5]
          #[0 "\300\301\302\303\304$\207"
            [add-hook change-major-mode-hook org-babel-show-result-all 
append local] 5]
          org-babel-result-hide-spec org-babel-hide-all-hashes)
  org-export-headline-levels 888
  org-latex-format-drawer-function #[514 "\207" [] 3 "\n\n(fn _ CONTENTS)"]
  org-icalendar-use-scheduled '(event-if-not-todo event-if-todo-not-done)
  org-confirm-shell-link-function 'yes-or-no-p
  org-export-with-date nil
  org-html-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME 
  outline-isearch-open-invisible-function 'outline-isearch-open-invisible
  org-export-with-todo-keywords nil
  org-icalendar-include-todo 'all
  org-export-initial-scope 'subtree
  org-odt-format-headline-function 'org-odt-format-headline-default-function
  org-export-with-statistics-cookies nil
  org-agenda-before-write-hook '(org-agenda-add-entry-text)
  org-export-with-author nil
  org-src-mode-hook '(org-src-babel-configure-edit-buffer 
  org-confirm-elisp-link-function 'yes-or-no-p
  org-export-with-timestamps nil
  org-speed-command-hook '(org-speed-command-activate 
  org-ascii-format-inlinetask-function 'org-ascii-format-inlinetask-default
  org-export-with-tags nil
  org-odt-format-drawer-function #[514 "\207" [] 3 "\n\n(fn NAME CONTENTS)"]
  org-persist-directory "c:/Users/KC/AppData/Local/Temp/org-persist-KWkfxv"
  org-icalendar-combined-name "icalendar-org-agenda"
  org-export-backends '(html icalendar latex odt)
  org-icalendar-combined-description "icalendar-org-agenda-files"
  org-fold-core-isearch-open-function 'org-fold--isearch-reveal
  org-persist-before-write-hook '(org-element--cache-persist-before-write)
  org-tab-first-hook '(org-babel-hide-result-toggle-maybe 
  org-link-shell-confirm-function 'yes-or-no-p
  org-babel-pre-tangle-hook '(save-buffer)
  org-agenda-loop-over-headlines-in-active-region nil
  org-occur-hook '(org-first-headline-recenter)
  org-export-with-drawers t
  org-metadown-hook '(org-babel-pop-to-session-maybe)
  org-link-parameters '(("attachment" :follow org-attach-follow :complete
                ("id" :follow org-id-open)
                ("eww" :follow org-eww-open :store org-eww-store-link)
                ("rmail" :follow org-rmail-open :store org-rmail-store-link)
                ("mhe" :follow org-mhe-open :store org-mhe-store-link)
                ("irc" :follow org-irc-visit :store org-irc-store-link 
                ("info" :follow org-info-open :export org-info-export :store
             org-info-store-link :insert-description
                ("gnus" :follow org-gnus-open :store org-gnus-store-link)
                ("docview" :follow org-docview-open :export 
org-docview-export :store
                ("bibtex" :follow org-bibtex-open :store 
                ("bbdb" :follow org-bbdb-open :export org-bbdb-export 
             org-bbdb-complete-link :store org-bbdb-store-link)
                ("w3m" :store org-w3m-store-link)
                ("doi" :follow org-link-doi-open :export 
                ("file+sys") ("file+emacs") ("shell" :follow 
                ("news" :follow
             #[514 "\301\300\302\x04Q\x02\"\207" ["news" browse-url ":"] 6
               "\n\n(fn URL ARG)"]
                ("mailto" :follow
             #[514 "\301\300\302\x04Q\x02\"\207" ["mailto" browse-url ":"] 6
               "\n\n(fn URL ARG)"]
                ("https" :follow
             #[514 "\301\300\302\x04Q\x02\"\207" ["https" browse-url ":"] 6
               "\n\n(fn URL ARG)"]
                ("http" :follow
             #[514 "\301\300\302\x04Q\x02\"\207" ["http" browse-url ":"] 6
               "\n\n(fn URL ARG)"]
                ("ftp" :follow
             #[514 "\301\300\302\x04Q\x02\"\207" ["ftp" browse-url ":"] 6
               "\n\n(fn URL ARG)"]
                ("help" :follow org-link--open-help :store 
                ("file" :complete org-link-complete-file)
                ("elisp" :follow org-link--open-elisp))
  org-metaup-hook '(org-babel-load-in-session-maybe)
  org-icalendar-combined-agenda-file "~/2-Areas_R/NOTAS/org-mode-agenda.ics"
  org-icalendar-categories nil
  org-export-preserve-breaks t

On 02/02/2024 17:53, Ihor Radchenko wrote:
> Ypo<ypuntot@gmail.com>  writes:
>> 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.
> You can just do it on timer or when the file changed.
>> 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.
> It would help if you provided an MWE. Seehttps://orgmode.org/manual/Feedback.html#Feedback
> It is extremely hard to diagnose things blindly.

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

  reply	other threads:[~2024-02-02 21:17 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             ` Ypo [this message]
2024-02-02 21:25               ` [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: " 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=532da0f8-b93e-6e21-8ea4-0046808585ed@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).