Re: Order of Options Processing

We may have a few at a disadvantage so I'll explain things a bit, throw in my two cents, and let others respond.

# I really prefer it when
# my command line options are *it*, so to speak. When
# something doesn't work quite right, I don't really like
# having to 1) remember that I have a configuration file
# out there (since I've never used one before this
# release - okay, call me lazy ;-) and 2) figure out
# which option(s) in the configuration file (as there
# are quite a few!) are conflicting with my command line
# options.

First... The use of a configuration file is totally optional. If you want to use it, do so. If not, don't. If you don't use one, your command line is it. ;) Second, they can be commented. ;) The hmrc.html is a useable example. Maybe a bit more commenting in the supplied config files would help. :-)

In the original version of Hypermail the order of processing was

1. Defines in config.h
2. Environment Variables
3. Command line options
4. Configuration file variables.

If you used a configuration file everything on the command line was basically ignored. If you wanted to make a temporary run with different options then you'd have to edit the configuration file to make the changes. You'd later have to remember to change it back or it would keep using your "temporary" options.

In the current version, the order of processing is

1. Defines in config.h
2. Environment Variables
3. Configuration file variables.
4. Command line options

The command line options override the defaults that you have previously set so a temporary run means running it with different command line options set. This is different in that in you now inherit the values of the configuration file before the options on the command line are processed. Before you could not mix the two at all.

Now you can have multiple lists that you want to look the same use a single config file and then specify the list specific "listname", "About" URL, and "Other Archives" URL on the command line. The config file will have the template files and other common items set. At the same time you can have additional lists that do or don't use config files as desired.

Config files were there before. I changed their useage according to requests Kevin received. (I've also now converted all the lists on landfield.com to use them. Really much easier to manage than having to remember the compiled in defaults...)

-- 
Kent Landfield                        Phone: 1-817-545-2502             
Email: kent_at_landfield.com             http://www.landfield.com/
Email: kent_at_nfr.net                   http://www.nfr.net/
Please send comp.sources.misc related mail to kent_at_landfield.com
Search the Usenet Hypertext FAQ Archive at http://www.faqs.org/faqs/