Specifying an alternate config file on the command line as any of the following results in an immediate dialog box saying, "Failed to execute script tagger":
picard.exe --config-file C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini
picard.exe --config-file=C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini
picard.exe --config-file "C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini"
picard.exe --config-file="C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini"
picard.exe -c C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini
picard.exe -c=C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini
picard.exe -c "C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini"
picard.exe -c="C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini"
Specifying an alternate config file on the command line as any of the following results in Picard starting with the default configuration settings and not those specified in the INI file:
picard.exe -c r"C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini"
picard.exe -c=r"C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini"
picard.exe --config-file r"C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini"
picard.exe --config-file=r"C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini"
I don't know what I was doing wrong before, but I just tried again with the following command lines, and Picard used the specified INI file as it was supposed to. I am unable to recreate the problem I encountered earlier. I suggest that this ticket be closed. If I encounter the problem again, I'll try to gather more information to help determine the cause of the problem.
picard.exe --config-file C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini
picard.exe --config-file "C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini"
picard.exe -c C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini
picard.exe -c "C:\Users\bob\AppData\Roaming\MusicBrainz\PicardTest.ini"