Quoting Nicolas Rachinsky <[EMAIL PROTECTED]> [Mar 22, 2002 06:20]:
> * Cameron Simpson <[EMAIL PROTECTED]> [2002-03-22 12:24:10 +1100]:
> > Someone has already mentioned his startup file being:
> > 
> >     source "shell-cmd |"
> > 
> > Wouldn't:
> > 
> >     macro foo :source "shell-cmd|"
> > 
> > be general enough  to go most algorithmic things without
> > bloating mutt? The shell hcan hand of to whatever interpreter
> > tickles your fancy.
> 
> How can I get the "current" settings/status information into
> the script? For example, the value of editor, or the number of
> unread messages.

Simple -- make shell-cmd write out a config file as a side
effect, and, when it starts, it can read the current config file
and use it as a base.

(darren)

-- 
There are two ways of constructing a software design. One way is
to make it so simple that there are obviously no deficiencies.
And the other way is to make it so complicated that there are no
obvious deficiencies.
    -- C.A.R. Hoare

Reply via email to