[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nmh-workers] Locking In Scripts and nmh Locking
From: |
David Levine |
Subject: |
Re: [Nmh-workers] Locking In Scripts and nmh Locking |
Date: |
Thu, 26 Apr 2012 17:05:15 -0400 |
Ralph wrote:
> David Levine wrote:
> > Would a don't-modify-any-internal-nmh-state switch to pick would have
> > solved that problem?
>
> Do the MH, MHCONTEXT, and $MH's mh-sequences entry help solve some of
> the problems by having the cron jobs set up their own environment, or
> use one pre-set up for them, if their desired side-effects are
> restricted to refiling emails, etc?
>
> http://rand-mh.sourceforge.net/book/mh/shomes.html#MuMHSe
Yes!
David
$ folder -f
inbox
$ pick +test last
1
$ folder -f
test
$ folder +inbox -f
inbox
$ MHCONTEXT=/dev/null pick +test last
1
$ folder -f
inbox
- Re: [Nmh-workers] Locking In Scripts and nmh Locking, (continued)
Re: [Nmh-workers] Locking In Scripts and nmh Locking, David Levine, 2012/04/26
Re: [Nmh-workers] Locking In Scripts and nmh Locking,
David Levine <=
Re: [Nmh-workers] Locking In Scripts and nmh Locking, David Levine, 2012/04/27