![]()
From: Craig A Summerhill (craig@cni.org)
Date: Mon Apr 12 1999 - 15:52:04 CDT
On Mon, 12 Apr 1999, Daniel Stenberg <daniel.stenberg@autodiagnos.se> wrote:
>
> Craig A Summerhill wrote:
> >
> > > How are your feelings about this today?
> >
> > Well, if somebody wants to strip the comments, it could be easy enough
> > piping the command to a 'grep -v'.
> >
> > csh> hypermail -c /path-to/.hmrc -v | grep -v '^#' | grep -v '^$'
>
> Indeed.
>
> > But this doesn't really help generate a blank template, unless your
> > .hmrc config file has *all* the variables displayed in it.
>
> Surely it does? It always outputs all the variables it knows about.
> It displays all unchanged as commented and the ones that were set in
> the config file uncommented.
Not if you pipe the "hypermail -v" into a "grep -v" to eliminate the
comment lines. The current output from the hypermail -v flag is to
include all unspecified variables as comments in the output. E.g.
# Define path as the path to a template file containing
# valid HTML formatting statements you wish to use at the
# bottom of every message page.
#mhtmlfooterfile =
It does look like the output puts a "# " before the actual comments
for each variable and simply a "#" before the variable name. I suppose
modifying my command above to this does the trick for building a
template (note the inclusion of a space after the "#"):
csh> hypermail -c /path-to/.hmrc -v | grep -v '^# ' | grep -v '^$'
> I made the internal function capable of generating a list of only the
> variables actually set in the config file (or by environment variables)
> so it would be very easy to add in case we want it.
Just a curiosity, but since you effectively did away with the options.h
file, how does one compile with a global environment variable?
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.
-- Craig A. Summerhill, Systems Coordinator and Program Officer Coalition for Networked Information 21 Dupont Circle, N.W., Washington, D.C. 20036 Internet: craig@cni.org AT&Tnet (202) 296-5098
![]()