From: Ihor Radchenko <email@example.com>
To: "Robert Jäschke" <firstname.lastname@example.org>
Subject: Re: (org-icalendar-combine-agenda-files t) prints byte code
Date: Fri, 03 Mar 2023 16:20:56 +0000 [thread overview]
Message-ID: <87ilfh4xhz.fsf@localhost> (raw)
Robert Jäschke <email@example.com> writes:
>>> 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.
>> Just add an extra --eval "t" or something along that lines.
> Do you mean
> emacsclient --eval "(org-icalendar-combine-agenda-files t)" --eval "t"
> This still results in "#[514 "\302!\303!\304=\205B" being printed on STDOUT.
No idea then.
> Is there some way to figure out what's happening and why? (I'd really
> like to understand.)
You can try debugging to figure out at which place in the code the
output is triggered.
#[...] structure looks like a byte-compiled function object.
> Another issue is that the above call works in a shell but not when
> called by cron (both result in the strange output but with cron no file
> is created). I am not sure if that's relevant. I'd like to fix both
> issues but first things first. ;-)
It would help if you create a reproducer, so that we can test things on
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>
prev parent reply other threads:[~2023-03-03 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 10:56 (org-icalendar-combine-agenda-files t) prints byte code Robert Jäschke
2023-02-17 11:07 ` Ihor Radchenko
2023-03-02 12:20 ` Robert Jäschke
2023-03-03 16:20 ` Ihor Radchenko [this message]
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 \
* 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).