From: Ihor Radchenko <yantar92@gmail.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: 40838@debbugs.gnu.org
Subject: bug#40838: 28.0.50; [feature/native-comp] Function overrides in init.el are not honored after deferred compilation
Date: Sat, 23 May 2020 23:23:59 +0800 [thread overview]
Message-ID: <877dx2llo0.fsf@localhost> (raw)
In-Reply-To: <xjfv9kmvhq0.fsf@sdf.org>
> I believe if you want to have to workaround effective in deferred
> compilation you'll need to put the definition of these two functions
> into `comp-async-env-modifier-form' as discussed.
>
> Perhaps the best thing if to ask them to do it given they have a branch
> to support native-comp.
Never mind my last email. I thought that defun statements before
require should not be overridden, which is obviously wrong.
Best,
Ihor
Andrea Corallo <akrl@sdf.org> writes:
> Ihor Radchenko <yantar92@gmail.com> writes:
>
>>> If this is what is happening with straight.el, then my recipe is not
>>> actually reproducing my initial bug report. I have other cases when
>>> functions redefined in my config are overridden by initial definition
>>> when .eln is loaded. I think that I still need to investigate for a real
>>> recipe then.
>>
>> I have recently tried to find a temporary workaround to this issue with
>> straight.el+org+native-comp. However, my workaround seems to fail
>> because of native-comp (at least, I believe so).
>
> Hi Ihor,
>
> I believe if you want to have to workaround effective in deferred
> compilation you'll need to put the definition of these two functions
> into `comp-async-env-modifier-form' as discussed.
>
> Perhaps the best thing if to ask them to do it given they have a branch
> to support native-comp.
>
> Andrea
>
> --
> akrl@sdf.org
--
Ihor Radchenko,
PhD,
Center for Advancing Materials Performance from the Nanoscale (CAMP-nano)
State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China
Email: yantar92@gmail.com, ihor_radchenko@alumni.sutd.edu.sg
next prev parent reply other threads:[~2020-05-23 15:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 8:14 bug#40838: 28.0.50; [feature/native-comp] Function overrides in init.el are not honored after deferred compilation Ihor Radchenko
2020-04-25 9:16 ` Andrea Corallo
2020-04-25 14:26 ` Andrea Corallo
2020-04-26 4:55 ` Ihor Radchenko
2020-04-26 8:59 ` Andrea Corallo
2020-04-28 14:40 ` Ihor Radchenko
2020-04-28 15:03 ` Andrea Corallo
2020-05-18 15:23 ` Ihor Radchenko
2020-05-18 20:15 ` Andrea Corallo
2020-05-18 21:01 ` Andrea Corallo
2020-05-19 3:06 ` Ihor Radchenko
2020-05-23 14:13 ` Ihor Radchenko
2020-05-23 14:39 ` Andrea Corallo
2020-05-23 15:23 ` Ihor Radchenko [this message]
2020-06-02 7:27 ` Andrea Corallo
[not found] ` <87zh7ltgc7.fsf@localhost>
2020-07-28 7:24 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-07-28 9:06 ` Ihor Radchenko
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dx2llo0.fsf@localhost \
--to=yantar92@gmail.com \
--cc=40838@debbugs.gnu.org \
--cc=akrl@sdf.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs.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).