> On Apr 21, 2022, at 7:12 PM, Ken Hornstein wrote:
>
>>> You see, nmh's dirty secret (ok ok, one of many!) is that the
>>> first thing every command does is read the entire directory.
>>> Yep, the whole thing.
>>
>> If you use any syscall tracer, you will see that this is not what
>>
>> You see, nmh's dirty secret (ok ok, one of many!) is that the
>> first thing every command does is read the entire directory.
>> Yep, the whole thing.
>
>If you use any syscall tracer, you will see that this is not what
>happens. scan & pick will do a directory read only if no messages
>are
On Apr 21, 2022, at 1:21 PM, Eric Gillespie wrote:
>
> You see, nmh's dirty secret (ok ok, one of many!) is that the
> first thing every command does is read the entire directory.
> Yep, the whole thing.
If you use any syscall tracer, you will see that this is not what
happens. scan & pick will
I thought I would sit back and wait to see where this went.
I was surprised and disappointed no one brought up the huge
performance cost of the current implementation.
I guess no one has network-mounted home directories anymore.
I don't. But for many years that was where my mail lived.
And lots
Hi David,
> I rely on the exit status of build_nmh, and only look at the log file
> if indicates failure.
Ah, I was considering any tests skipped as failure because I was trying
to get them all to run. :-) I agree in the general case that's not
wanted.
> Should we output the summary to the
Hi David,
> > > Both releases saw a spew of "Broken pipe" errors after
> > > test-mhparam, not sure if that's expected or not.
> >
> > That's not expected. The test immediately after that test-mhparam
> > is test/oauth/test-send.
So Jay's later email showed EPIPE was being returned and that
Hi Eric,
> I've pushed f188de902b613110d5943210f212adb680a2b44a to master
> now, which should resolve this test failure.
Thanks, but could you, and any other committers, try to use Git's
rebase rather than merge as it preserves your commits and their messages
rather than ‘Merge commit
