My initial idea for configuration was to include a default config, the ability to define items using a configuration file, and to accept command line arguments. According to this approach, the working configuration should have been the combination of all three in the order listed, with the default being overwritten by the configuration file and the sum of the two being overwritten by command line arguments, making the latter more powerful than the former two. Admittedly, my own laziness often led me to rely on the default configuration, which was sufficient in most cases. While I understand that having a default for only one user is not necessary, I believe that other users with similar tendencies might appreciate such a feature. Since we cannot provide a custom binary, perhaps we could define a default configuration file name that is used when the binary is called without arguments.
@alessandrocarminati 's comment:
My initial idea for configuration was to include a default config, the ability to define items using a configuration file, and to accept command line arguments. According to this approach, the working configuration should have been the combination of all three in the order listed, with the default being overwritten by the configuration file and the sum of the two being overwritten by command line arguments, making the latter more powerful than the former two. Admittedly, my own laziness often led me to rely on the default configuration, which was sufficient in most cases. While I understand that having a default for only one user is not necessary, I believe that other users with similar tendencies might appreciate such a feature. Since we cannot provide a custom binary, perhaps we could define a default configuration file name that is used when the binary is called without arguments.