Mikko Hänninen <[EMAIL PROTECTED]>:
> This would be changed if there indeed were a command to change the
> current environment variables, like has been suggested. Maybe for
> 1.3...
I did send out a patch which adds the command "setenv" to Mutt.
Perhaps I should check it still works and ask J
Martti Rahkila <[EMAIL PROTECTED]> wrote on Mon, 27 Mar 2000:
> > > source ~/.mutt/colors.`if [ "$TERM" = "linux" ] ; then echo linux ; else echo
>default ; fi`
>
> Excellent tip: if I store the profile setting in an environment variable,
> I can test it and only load profile if it is not alread
On Sun, 26 Mar 2000, Mikko Hänninen wrote:
> Thomas Roessler <[EMAIL PROTECTED]> wrote on Sun, 26 Mar 2000:
> > His point is that he'd like to be able to use the new
> > unhook command in the beginning of each profile, and load
> > standard hooks at the right place from a different file.
>
> If
Thomas Roessler <[EMAIL PROTECTED]> wrote on Sun, 26 Mar 2000:
> His point is that he'd like to be able to use the new
> unhook command in the beginning of each profile, and load
> standard hooks at the right place from a different file.
If you say so. :-)
> >> Known problems/questions: - Is the
On 2000-03-25 18:19:01 +0200, Mikko Hänninen wrote:
> If that doesn't answer you, could you please give a few
> more details..?
His point is that he'd like to be able to use the new
unhook command in the beginning of each profile, and load
standard hooks at the right place from a different file.
Martti Rahkila wrote:
> - what would be an elegant way to include "forget-passphrase" command
> either in the macro or the profile?
Untested, at the bottom of each profile file:
push "\Cf"
christian
Martti Rahkila <[EMAIL PROTECTED]> wrote on Sat, 25 Mar 2000:
> 3) Check that muttrc doesn't contain any of the profile definitions,
> I noticed that muttrc defaults and/or send-hooks will override
> some of these! (Should it do that?)
I'm not sure I understand what you mean by your description.
