> > So, it wipes anything we try to set.
> > we use the -p to Preserve any old environment, and it wipes it...
> >
> > it would be usefull to preserve the env var :
> >
> > procmail ~/.procmailrc VERBOSE=on LOGFILE=`tty` < /tmp/[...]
> >
> > that would be nice if there was a way to divert values from the default,
> > to test.
>
> Have you tried using both "-p" and "-m"? From the manpage:
>
> If both -p and -m are specified, the list of preset environment
> variables shrinks to just: LOGNAME, HOME, SHELL, ORGMAIL and MAILDIR.
the problem is that i'm trying to set VERBOSE and LOGFILE,
so i can't use -m
>
> If that's still not enough you could even use something like this
> in your .procmailrc file:
>
> :0
> * MYMAILDIR ?? .
> { MAILDIR=$MYMAILDIR }
>
> and this on the command line:
>
> procmail MYMAILDIR=foo < some-message
>
>
> So I don't think we need a new procmail feature for this.
ok, so i could do
VERBOSE=off
:0
* MYVERBOSE ?? .
{ VERBOSE=$MYVERBOSE }
and call procmail MYVERBOSE=on < some-message
right ?
but all that is a workaround to set env var on the command line...
i believe overriding env. var. with values in the rc file
is wrong, if you specify them on the command line, it means
that you want to change it, right ?
in what case, if you call procmail with the -p option,
would you like your env. var. wiped ?
in every other tools the command line switchs and env. var.
have precedence over the config file...
thanks
--
xavier
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
