Ken wrote:
> If you install it the "normal" way, it download a pre-built binary
> distribution that doesn't know about things you installed like w3m that
> might be useful for displaying HTML content.
The RPM spec generates it through "make install". /etc/mhn.defaults
is a make target. (So it w
I did the brew (packaging system for MacOS X) Formula for nmh and that
worked out pretty well, but there's one wrinkle.
If you install it the "normal" way, it download a pre-built binary
distribution that doesn't know about things you installed like w3m that
might be useful for displaying HTML con
Ralph wrote:
> It occurs to me that it may be quicker to write tests that aim to
> increase coverage rather than test actual output against expected, etc.
> That would then give valgrind more to chew on. They could then be
> fleshed out separately, especially if they were marked in some way, to
>
Hi David,
> Not 100%, so your point is well taken, but higher than I expected.
It occurs to me that it may be quicker to write tests that aim to
increase coverage rather than test actual output against expected, etc.
That would then give valgrind more to chew on. They could then be
fleshed out s
Lyndon wrote:
> But how much code coverage do we actually get?
82% of the lines that Ralph touched recently are covered. (Based on join of
git blame and gcov outputs.) Not 100%, so your point is well taken, but higher
than I expected.
David
___
Nmh-
