Josh Bresser's test suite is now integrated into the
Makefile. "make test" runs it. And builds nmh if needed
and you want to do both with one command.
It already caught two code errors: a segfault in "new" due
to an uninitialized variable and a recent regression in the
display of timezone. And
On 2012-02-07, at 10:13 AM, Joel Uckelman wrote:
> What you're describing here is far beyond what I was intending; I only
> want a seamless way to apply my eyeballs to these broken messages.
I don't think it gets any more seamless than cat. I would have show (and
anything else) print the full p
Thus spake Lyndon Nerenberg:
>
> all
> > such nonconforming mail in the bin. That said, when I get mail from
> > ConfMaster, it tends to be mail that I need to read, so I appreciate =
> it
> > when nmh can take a guess and perhaps show me some not-too-garbled =
> text.
> > (In this particular case
On Tue, Feb 7, 2012 at 11:46 AM, Joel Uckelman wrote:
> My suggestion, then, is this: Could we both have some indication that
> the input is bad, *and* have nmh make an attempt at interpreting it?
-1
You can already invoke show to disable MIME processing, so
when you encounter such a message, ju
On 2012-02-07, at 9:29 AM, Lyndon Nerenberg wrote:
> being liberal about what you except
Oh good lord, did I really write that?!? :-)
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers
> I would love to be able to prevail upon them to fix this or to dump all
> such nonconforming mail in the bin. That said, when I get mail from
> ConfMaster, it tends to be mail that I need to read, so I appreciate it
> when nmh can take a guess and perhaps show me some not-too-garbled text.
> (In
On Mon, Feb 6, 2012 at 12:51 PM, Joel Uckelman wrote:
>> If/when IMAP support is added in, mhpath will return
>> imap URLs. If one is using the existing classic storage
>> model, then local pathnames are returned.
>
> IMAP URLs aren't paths, at least not in the sense I take 'path' to have
> in 'm
On Tue, Feb 7, 2012 at 11:29 AM, Lyndon Nerenberg wrote:
>> But do you really think that
>> should be the only resort when badly formed mail arrives? I'd prefer to
>> see what was intended by the sender.
>
> Yes, I do :-( QP and Base64 (and MIME in general) have been around for
> nearly two dec
Thus spake Lyndon Nerenberg:
>
> On 2012-02-07, at 7:37 AM, Oliver Kiddle wrote:
>
> > But do you really think that
> > should be the only resort when badly formed mail arrives? I'd prefer to
> > see what was intended by the sender.
>
> Yes, I do :-( QP and Base64 (and MIME in general) have bee
On 2012-02-07, at 9:36 AM, Lyndon Nerenberg wrote:
> this means MH would keep a local cache of the content on the IMAP server.
Doh. The local cache would, obviously, be kept locally, not on the server.
___
Nmh-workers mailing list
Nmh-workers@nongnu.
There seem to be a few misconceptions about how IMAP works. Let me try to
explain in a bit more detail about how I think IMAP would work with MH.
First, and perhaps most important, IMAP support does not preclude keeping local
copies of the message content in the native MH store. MH would grow
On 2012-02-07, at 7:37 AM, Oliver Kiddle wrote:
> But do you really think that
> should be the only resort when badly formed mail arrives? I'd prefer to
> see what was intended by the sender.
Yes, I do :-( QP and Base64 (and MIME in general) have been around for nearly
two decades now. If the
On 2/7/2012 3:37 PM, Oliver Kiddle wrote:
> Lyndon Nerenberg wrote:
>> Or you could use cat(1).
> Well that's what I do do.
>
> It's great that MH makes that easy and there are various situations in
> which I will go straight to the file. But do you really think that
> should be the only resort whe
Lyndon Nerenberg wrote:
> On 2012-02-07, at 3:00 AM, Oliver Kiddle wrote:
> > I'd prefer to just see the email. mhshow could have a -pedantic or -lint
> > option.
>
> Or you could use cat(1).
Well that's what I do do.
It's great that MH makes that easy and there are various situations in
which I
>ps...
>If all you want from mh is "show/next/comp/repl/rmm" you might just as well
>use thunderbird, or sylpheed, or even outlook express.
Not even that's true. Such a user still has all the power of a Unix shell.
For example, if she is using bash:
% !scan
or
% show irs | egrep -i 'penalty|as
On 2/7/2012 2:36 PM, Ken Hornstein wrote:
>> ... (nb:
>> this is not to denigrate IMAP. For people whose needs it serves, it is
>> just fine, it is just that those needs, and MH's requirements, aren't
>> compatible.)
> Well, people have made what I consider reasonable arguments in terms of
> use c
>I don't understand that, I've used multiple identities, without any
>particular difficulties, for a long time now (> 20 years), and MH (and
>later nmh) just works as it is. That is, to say, in this area I see
>no need for any changes, and consequently no need for any code to be
>developed.
Well,
On 2012-02-07, at 3:00 AM, Oliver Kiddle wrote:
> I'd prefer to just see the email. mhshow could have a -pedantic or -lint
> option.
Or you could use cat(1).
___
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo
To me, Ken's suggestions here sound good.
In just about every installation of nmh I've ever had, the first thing I
do is to set masquerdade: draft_from. (Currently, I have exim configured
to choose an appropriate smarthost based on the From address. I have
From: set in my draft as part of my promp
Robert Elz writes:
>If all you want from mh is "show/next/comp/repl/rmm" you might just as
>well use thunderbird, or sylpheed, or even outlook express - they all
>provide methods to read, delete, reply, ... to e-mail, and usually with
>a user interface that is easier to master.
Don't be so sure
Date:Tue, 07 Feb 2012 01:53:04 -0500
From:Ken Hornstein
Message-ID: <201202070653.q176r4r9026...@hedwig.cmf.nrl.navy.mil>
| Well, here's the problem ... it's easy for you to say that, isn't it?
| I mean, you're not the one doing the coding. :-/
Believe me, I unde
21 matches
Mail list logo
