[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Finalizing 'inhibit-automatic-native-compilation'
From: |
Eli Zaretskii |
Subject: |
Re: Finalizing 'inhibit-automatic-native-compilation' |
Date: |
Thu, 02 Feb 2023 11:18:06 +0200 |
> Date: Thu, 2 Feb 2023 09:41:46 +0100
> From: <tomas@tuxteam.de>
>
> > What I'm interested in is hearing the _reasons_ why you decided to go
> > with the environment variable, because those reasons might be
> > important in other uses. Was it just the convenience, or was it
> > something else?
>
> I think one was put forward in the original:
>
> "one reason is that we need to handle invocations of Emacs deep
> within third party Makefiles."
Which is exactly why using environment variables is a bad idea, IME.
Who says the third-party packages are ready for this?
- Re: Finalizing 'inhibit-automatic-native-compilation', (continued)
- Re: Finalizing 'inhibit-automatic-native-compilation', Aymeric Agon-Rambosson, 2023/02/09
- Re: Finalizing 'inhibit-automatic-native-compilation', Eli Zaretskii, 2023/02/09
- Re: Finalizing 'inhibit-automatic-native-compilation', Aymeric Agon-Rambosson, 2023/02/10
- Re: Finalizing 'inhibit-automatic-native-compilation', Eli Zaretskii, 2023/02/10
- Re: Finalizing 'inhibit-automatic-native-compilation', Andrea Corallo, 2023/02/10
Re: Finalizing 'inhibit-automatic-native-compilation', Sean Whitton, 2023/02/02
Re: Finalizing 'inhibit-automatic-native-compilation', Liliana Marie Prikler, 2023/02/04
Re: Finalizing 'inhibit-automatic-native-compilation', Andrea Corallo, 2023/02/13