Turns out we already disable EnvVar expansion when reading the kicad config.
If we write EnvVar syntax out, then I think we’re expecting to get it back in
(thus the issue with the kicad config). So for other configs the enabled
EnvVar expansion would only make a difference if you hand-edited the config
file, and we’re going to overwrite it the next time the app is run anyway so
that seems of limited use.
> On 3 Aug 2018, at 23:59, Jeff Young wrote:
>
> I noticed that we spend a lot of time processing EnvVars in wxConfigBases
> when starting apps (to the tune of 10%, believe it or not).
>
> Do we even have any EnvVars in config settings? (Ones that we want expanded
> on the way in, rather than ones that are just stored as text?)
> ___
> Mailing list: https://launchpad.net/~kicad-developers
> Post to : kicad-developers@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kicad-developers
More help : https://help.launchpad.net/ListHelp
