ralph wrote:
> Jeffrey Honig wrote:
> > Here's MTR's answer:
> >
> > ``when you run mh commands in a script, you want all the defaults to
> > be what the man page says. when you run a command by hand, then you
> > want your own defaults...
> >
> > /mtr''
>
> So scan(1), etc., in a script should ignore ~/.mh_profile?
whether any particular UI component is appropriate or useful in a
script has probably changed over time -- i suspect what people
are willing to script has become far more sophisticated over the
lifetime of mh.
if it's important to be able to ignore a user's .mh_profile during
execution, then a (new? maybe it exists already) "-noprofile" option
would seem like the right implementation. or, what i think already
exists (though i haven't tried it):
MH=/dev/null <program-name>
paul
>
> Cheers, Ralph.
>
> _______________________________________________
> Nmh-workers mailing list
> [email protected]
> https://lists.nongnu.org/mailman/listinfo/nmh-workers
=---------------------
paul fox, [email protected] (arlington, ma, where it's 22.5 degrees)
_______________________________________________
Nmh-workers mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/nmh-workers
