Robert Jäschke 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
>
>
Dear Ihor,
Am 17.02.23 um 12:07 schrieb Ihor Radchenko:
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.
Just
Robert Jäschke writes:
> (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
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