Previously the logic that updates autoexec.cfg and server.cfg on
startup used single quotes in the call to sed. Double quotes are
required to actually replace the environment variable name with
its content, though.
@kaimallea Not sure why I didn't see the issue earlier, probably because it was masked by 'sed -i -n' actually emptying the whole file anyway. Sorry about this.
To be honest I am wondering how this config file update logic worked for anyone before. Maybe no one else ran into these issues because it was introduced only recently?
Previously the logic that updates autoexec.cfg and server.cfg on startup used single quotes in the call to sed. Double quotes are required to actually replace the environment variable name with its content, though.
@kaimallea Not sure why I didn't see the issue earlier, probably because it was masked by 'sed -i -n' actually emptying the whole file anyway. Sorry about this. To be honest I am wondering how this config file update logic worked for anyone before. Maybe no one else ran into these issues because it was introduced only recently?