hugbug wrote: ↑20 Mar 2019, 15:55
Searching in install dir first is very important. That makes a new installation with installer into a new directory a clean and always working installlation, an important thing for troubleshooting.
On a M$ system, I agree with using the config file in the installdir as the first choice. But, on a Linux/Unix system, the concept of searching the user's home first goes way back. For me, that is over 35 years. If the program is started by root, or at startup, then a home config file won't necessarily be found/created. Then a /etc location would be searched next. In this case usually a place like /etc/nzbget/nzbget.conf. Lastly the installdir location.
I really hate how M$ tends to do configurations, i.e., via the registry. Way back when, the .ini file was used (and still is in some cases) and that was always in the installdir. While the concept of a home kinda exists in the "Documents and Settings" folder, I've never liked it. Being Unix born and bred, I like having my home searched first for the config file for programs I run. If I set up a program that is started by the system, then I expect a config file in /etc. In this case, I start nzbget in a terminal.
Now I see why the backup and restore of the config file exists. When an update of the program is installed, the config file will get overwritten. If the user forgets to back up the config fille, all is lost. By having the config file in $HOME, or .etc, one doesn't have to worry about losing the conifguration.
Consider me an old-timer. Obviously you have no plans to add this feature request. So, I'll just have an alias that starts nzbget with the -c option.
I don't mean to be a pain. I really do like this program. Once I get extracting the nzb file from a rar file working, I'll be really happy as this program makes downloading usenet files a breeze. Thanks.