<<< Date Index >>>     <<< Thread Index >>>

Re: expand mutt vars as we do environment vars



On Tuesday, 17 January 2006 at 16:14, Cameron Simpson wrote:
> On 16Sep2005 21:58, brendan cully <brendan@xxxxxxxxxx> wrote:
> | The attached patch causes mutt to expand mutt variables in the same
> | way that it expands environment variables. For example, you could do
> | something like this in a hook:
> | 
> | set sendmail="mysmtp -f $from"
> | 
> | A couple of gotchas: environment variables take precedence, and I
> | haven't gotten around to expanding them in a couple of places (notably
> | shell-escape).
> 
> Nifty.
> 
> Designwise, wouldn't it be better for mutt vars to have precedence over
> envvars? Personally, I generally expect the "inner" app to override
> outer stuff. I can imagine an unfortunate envvar damaging my mutt config
> with the current precedence.

I agree in principle. The code is the way it is only for backward
compatibility. I suppose another option would be to have mutt vars
take precedence but emit a warning when there is an env var with the
same name?

Attachment: pgpWFryJiAZ66.pgp
Description: PGP signature