Well title says it all.
I read that other thread about QMC2 portability and realized, that if QMC2 init was a bit smarter, it wouldn't (in most cases) need a parameter to define own .ini location.
Instead of using user home as first location for .qmc directory, it should first look in OWN working directory if the path exists.
OR if you want to keep user home as first location (which also makes sense), at least change the behavior so that if there is no .qmc in user directory, to then look for .qmc in working directory and use that AND ONLY IF there is no .qmc in working directory to then create .qmc in user directory.
This is a way more normalized process, that will allow for much more easier portable setups (with the help of relative paths in the config - as already allowed, which IIRC was also my request years ago and you implemented).