# > I'm wondering how other people feel about the current
# > order of options processing?
#
# I quite agree with your opinion as given below. It is both convenient and
# generally conventional for programs to treat command-line options as the
# highest priority, config file options next, and default options last.
#
# --Byron Darrah
#
# > 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.
# >
# > What are the pros to the current order that I'm missing?
# >
# > Cheers,
# > -Darci
Yes, this was exactly why it was done. Command line options need to have the highest priority and do in the latest version.
-- 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/Received on Tue 09 Jun 1998 01:33:37 AM GMT
This archive was generated by hypermail 2.2.0 : Thu 22 Feb 2007 07:33:49 PM GMT GMT