[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Nmh-workers] Inability to cat a Message Part.

From: David Levine
Subject: Re: [Nmh-workers] Inability to cat a Message Part.
Date: Sun, 28 Apr 2013 12:11:48 -0400

Ralph wrote:

> Hi David,
> > I quickly prototyped an -outfile switch to mhstore, let me
> > know if you want me to finish it up and add it.
> I think ~/bin/mhcat linked to mhstore might do me, thanks.

I might add it anyway, unless there's objection real soon.  I
often do mhstore+mv, this would save me a step.  That step is
non-trivial, it's actually
mhstore + look for the filename + copy that filename to the mv.

> > > One annoyance is mhstore/mhcat chucking `storing message 42 part 2 to
> > > stdout' on stderr.  I've tried -noverbose mentioned in the manual but it
> > > has no effect and is apparently the default anyway.  How does one shut
> > > it up?
> > 
> > One cannot :-/
> Is there anything that is currently controlled by -[no]verbose for
> mhstore?  The `storing' message would seem to be verbose to my eyes.

The -noverbose switch does absolutely nothing now.  I'd offer to
fix it, but after looking into it, it will be harder than adding
-outfile :-/  The proper fix would be to add an argument to
roughly a dozen internal mhstore functions.  (The mhlist
functions already have it.)  I'd rather not add the global, it
would be a hack.

> > Though with mhstore -outfile - 2>/dev/null, that's not necessary.
> True, though I dislike discarding the known unknowns so tend to do more
>     pick ... 2> >(sed '/^pick: no messages match specification$/d')
> to explicitly remove the known knowns.  :-)

I just tripped over that in the test, good idea.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]