It would be nice to have a special token representing $HOME like __PATH__home similar to how $0 is represented as __PATH__executable in config files. Maybe the more generic solution would be to allow any kind of environment variable substitution through __ENV__<var> instead of hardcoding for a usecase like HOME.
Right now I'm using sed hacks and binary wrapping to work around this shortcoming, but it would be nice to do this natively to prevent parsing incompatibilities in the future.
[0.15.25] Missing Path Expansion for HOME in .cfg and .ini
Moderator: ickputzdirwech
-
- Manual Inserter
- Posts: 1
- Joined: Fri Jun 30, 2017 7:34 am
- Contact:
Re: [0.15.25] Missing Path Expansion for HOME in .cfg and .ini
__PATH__system-write-data__ expands to ~/.factorio on Linux, %APPDATA%\Factorio on Windows and ~/Library/Application Support/factorio on MacOSX
Can you elaborate on what would you need environment variable expansion for and why modifying config instead of environment variable is not good enough option?
Can you elaborate on what would you need environment variable expansion for and why modifying config instead of environment variable is not good enough option?