emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-babel-load-file can not compile file
Date: Thu, 12 May 2022 21:55:43 +0700	[thread overview]
Message-ID: <t5j75h$dbo$1@ciao.gmane.io> (raw)
In-Reply-To: <877d6sjl6c.fsf@localhost>

On 11/05/2022 19:41, Ihor Radchenko wrote:
> Max Nikulin writes:
>> Actual result:
>>> Compiling /home/ubuntu/examples/org/ex-ob-load-file.el...done
>>> Wrote /home/ubuntu/examples/org/ex-ob-load-file.elc
>>> progn: Cannot open load file: No such file or directory, ex-ob-load-file.el
>> It seems, it is a regression caused by the Org commit
>> 0193b543e9ef84bfefe76d55e330d5b1cb842cef
>>> -	  (byte-compile-file tangled-file 'load)
>>> +	  (byte-compile-file tangled-file)
>>> +	  (load tangled-file)
> What if you substitute the load call with
> (load (byte-compile-dest-file tangled-file))?

I do not mind (of course if there is no plan to deprecate the function).

In addition, from my point of view, `byte-recompile-file' with 0 as the 
FORCE argument is more suitable than simple `byte-compile-file' since 
the former does not rewrite the compiled file when it is up to date.

  reply	other threads:[~2022-05-12 14:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10  7:34 [BUG] org-babel-load-file can not compile file Max Nikulin
2022-05-11 12:41 ` Ihor Radchenko
2022-05-12 14:55   ` Max Nikulin [this message]
2022-05-13 10:38     ` Ihor Radchenko
2022-05-13 10:38     ` Ihor Radchenko
2022-05-14 10:36       ` Max Nikulin
2022-05-14 11:35         ` Ihor Radchenko
2022-05-16 14:53           ` Max Nikulin

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='t5j75h$dbo$1@ciao.gmane.io' \
    --to=manikulin@gmail.com \
    --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).