Robert Jäschke <jaesc...@l3s.de> 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 our side. -- 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>