Mikko Hänninen <[EMAIL PROTECTED]>:
> Create a wrapper shell script which sets the variables and then calls
> qmail-inject (or the qmail sendmail wrapper if you prefer that). That's
> the only way to change those environment variables from the values that
> they had when Mutt started.
>
> > I tried using set signature="~/profiles/user1|" but that didn't work. I
> > figured it was due to the shell script only setting the varibles for that
> > shell and not the shell I am using.
>
> That is correct. The settings don't affect the environment that Mutt
> runs in. There is no way, that I know of, to change environment
> variables of a process from a sub-process. So that approach can't
> really work.
I can see it's not necessary in this particular case, but I wonder if
it would be useful to have a mutt command that calls setenv, so that
environment variables could be changed. Mutt execs quite a lot of
different programs that might be interested in the environment. You
can use wrapper scripts, of course, but a setenv command might be more
convenient in some cases. Maybe.
I'm not sure how mutt itself would behave if you changed LANG,
LC_TIME, etc, while it was running. I might just try it to see ...
Edmund
