Re: -v ?

On Tue, 13 Apr 1999, Daniel Stenberg <daniel.stenberg_at_autodiagnos.se> wrote:
>
> All the variables in the config file are set in this order:
>
> 1. Internal defaults
> 2. Environment variables
> 3. Config file items
> 4. Command line options
>
> If you have one of the environment variables set, I think it is used
> although it may not be shown uncommented in the -v output (since it
> wasn't used in the actual config file).
>
> Should I make it appear uncommented in such a case?

Personally, I think this makes sense. I *assumed* the output from the -v flag was telling me the settings in place (especially when used in combination with the -c flag to read an external .hmrc config file). If hypermail is using a setting from one of the four methods above it just make sense to me that it would appear uncommented in the -v output. Thus you can use the -v flag to output a .hmrc file which can be edited to your liking...

I have to say, I have been confused since I first started using Kevin's original 1.x hypermail in trying to determine which settings were being enforced when. Defaults behaviors used to be compiled in by editing the options.h file. But I have opted to put as much as possible in external .hmrc config files because I found I was getting totally unpredictable behaviors from hypermail on various executions otherwise. The down side of this is that I need to maintain a config file for each separate archive I want to markup -- which can be time consuming. But it works.

It would be so nice to be able to reliably review what settings are being used, and when...

> > On my binary (most recent I've installed is 2a16) the "hypermail -v"
> > alone returns all variables as commented out. I assume this means
> > there are no global environment variables compiled into my binary.
>
> The environment variables aren't "compiled into" hypermail, they're
> read when hypermail is invoked.

By "compiled in", I meant internal definitions, as per (1) in your list above.

With version 1.x of hypermail, some default behaviors otherwise handled internally could be compiled in with settings in the options.h file. Right? I understand the rationale for doing away with this, and think it is better now than before. But I am still not clear on what hypermail is doing to set default behaviors for various settings as per (2) in your list above.

Some default behaviors must be "compiled in" to hypermail as per (1) in your list above. If defaults are not compiled into the binary, and they are not specified as per (3) in your list above, from where are they read? Are you talking about shell environment settings?

-- 

   Craig A. Summerhill, Systems Coordinator and Program Officer
   Coalition for Networked Information
   21 Dupont Circle, N.W., Washington, D.C.   20036
   Internet: craig_at_cni.org   AT&Tnet (202) 296-5098