emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* (org-icalendar-combine-agenda-files t) prints byte code
@ 2023-02-17 10:56 Robert Jäschke
  2023-02-17 11:07 ` Ihor Radchenko
  0 siblings, 1 reply; 4+ messages in thread
From: Robert Jäschke @ 2023-02-17 10:56 UTC (permalink / raw)
  To: emacs-orgmode


[-- 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,
Robert





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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: (org-icalendar-combine-agenda-files t) prints byte code
  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
  0 siblings, 1 reply; 4+ messages in thread
From: Ihor Radchenko @ 2023-02-17 11:07 UTC (permalink / raw)
  To: Robert Jäschke; +Cc: emacs-orgmode

Robert Jäschke <jaeschke@l3s.de> 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 "(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 add an extra --eval "t" or something along that lines.

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: (org-icalendar-combine-agenda-files t) prints byte code
  2023-02-17 11:07 ` Ihor Radchenko
@ 2023-03-02 12:20   ` Robert Jäschke
  2023-03-03 16:20     ` Ihor Radchenko
  0 siblings, 1 reply; 4+ messages in thread
From: Robert Jäschke @ 2023-03-02 12:20 UTC (permalink / raw)
  To: Ihor Radchenko; +Cc: emacs-orgmode


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

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

Is there some way to figure out what's happening and why? (I'd really 
like to understand.)


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


Best regards,
Robert

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

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: (org-icalendar-combine-agenda-files t) prints byte code
  2023-03-02 12:20   ` Robert Jäschke
@ 2023-03-03 16:20     ` Ihor Radchenko
  0 siblings, 0 replies; 4+ messages in thread
From: Ihor Radchenko @ 2023-03-03 16:20 UTC (permalink / raw)
  To: Robert Jäschke; +Cc: emacs-orgmode

Robert Jäschke <jaeschke@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>


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-03-03 16:20 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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