emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Robert Jäschke" <jaeschke@l3s.de>
To: emacs-orgmode@gnu.org
Subject: (org-icalendar-combine-agenda-files t) prints byte code
Date: Fri, 17 Feb 2023 11:56:11 +0100	[thread overview]
Message-ID: <b13806e6-f541-7c4d-a1d3-52d776fae36c@l3s.de> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 631 bytes --]

Hi all,

(Likely since) After upgrading emacs from 27.1 to 28.2 and org mode from 
9.4.0 to 9.5.2 (i.e., from Debian stable to testing), 
org-icalendar-combine-agenda-files prints strange output when called 
(via cron) as follows:
emacsclient --eval "(org-icalendar-combine-agenda-files t)"

When I run this on the command line it prints (if I understand it 
correctly) Emacs byte code: #[514 "\302!\303!\304=\205B.
Running it non-asynchronously just prints nil.

Otherwise everything works but I would like to get rid of that output. 
Where/how could I start debugging this problem?

Best regards,

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2023-02-17 10:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 10:56 Robert Jäschke [this message]
2023-02-17 11:07 ` (org-icalendar-combine-agenda-files t) prints byte code Ihor Radchenko
2023-03-02 12:20   ` Robert Jäschke
2023-03-03 16:20     ` Ihor Radchenko

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=b13806e6-f541-7c4d-a1d3-52d776fae36c@l3s.de \
    --to=jaeschke@l3s.de \
    --cc=emacs-orgmode@gnu.org \


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