unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Andrea Corallo <akrl@sdf.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Stephen Leake <stephen_leake@stephe-leake.org>,
	emacs-devel <emacs-devel@gnu.org>
Subject: Re: native-comp and resetting of search paths
Date: Tue, 14 Jul 2020 10:41:26 -0400	[thread overview]
Message-ID: <jwvzh822mcn.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <xjfwo36h5ce.fsf@sdf.org> (Andrea Corallo's message of "Tue, 14 Jul 2020 08:24:17 +0000")

> Agree.  So far the only way I see to remove this directory dualism is
> what you have proposed here:
>
> https://lists.gnu.org/archive/html/emacs-devel/2020-06/msg00050.html

I must say I really like what this guy proposes.
He must be bright.

> This choice is key for making the native compiler project succeed or not
> (and interestly enough has nothing to do with the compiler it-self), so
> please if you have ideas on the topic don't esitate to share them :)

Indeed, I think we should strive to make it as transparent as possible:
compiling .el to .elc isn't transparent, but that doesn't mean we can't
make the compilation from .elc to .eln transparent.


        Stefan




      reply	other threads:[~2020-07-14 14:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 13:17 native-comp and resetting of search paths Alex Bennée
2020-07-13 18:15 ` Andrea Corallo via Emacs development discussions.
2020-07-13 19:51   ` Alex Bennée
2020-07-13 23:49     ` Stephen Leake
2020-07-14  5:49       ` Stefan Monnier
2020-07-14  8:04         ` Alex Bennée
2020-07-14  8:43           ` Andrea Corallo via Emacs development discussions.
2020-07-14  8:24         ` Andrea Corallo via Emacs development discussions.
2020-07-14 14:41           ` Stefan Monnier [this message]

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=jwvzh822mcn.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=akrl@sdf.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stephen_leake@stephe-leake.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).