Hi kre,
> case "$#" in
> 0) set -- cur;;
> esac
If this is bash(1) then
(($#)) || set cur
also works. ((...)) is arithmetic evaluation.
--
Cheers, Ralph.
dear Big I Down Under,
> It is this kind of thing that makes MH so nice.
indeed!
Date:Sat, 23 Nov 2019 20:26:27 +0530
From:Greg Minshall
Message-ID: <374462.1574520...@apollo2.minshall.org>
| combined with (new-fangled) bash "process substitution",
If you're planning on using this much, I'd suggest avoiding making bash
do all that work (and
Thus said Ralph Corderoy on Sat, 23 Nov 2019 12:03:42 +:
> Andy is correct. Mailman has a `nodupes' flag for every subscription
> and it's set for Andy's subscription.
Not any longer. :-)
I didn't realize I had control over this.
Andy
--
TAI64 timestamp: 40005dd9a302
Valdis Klētnieks wrote in <235182.1574454918@turing-police>:
|On Fri, 22 Nov 2019 20:51:52 +0100, Steffen Nurpmeso said:
|
|> I prefer people using Mail-Followup-To: instead of some ML
|> software modifying the address lists, they could as well just
|> avoid resending the mail!?! Yes, i
thanks to everyone for all the replies!
Ken suggested mhl. conveniently combined with (new-fangled) bash
"process substitution", the following does exactly what i want:
mhl -form <(echo received:split,compress,nowrap) `mhpath +inbox 794`
cheers, Greg
oof, ships crossing in the night -- thanks! (and for the
"-nomoreproc".)
> Hi Greg,
>
> > yes, awk and sed are in my repertoire, but, well, i was wondering if i
> > could avoid those in this case.
>
> For list's archive's completeness, the nmh way, using mhl(1) as Ken
> suggested, is
>
>
Hi Ken,
> Andy Bradford wrote:
> > Curiously, the email you sent me appears to have never arrived via
> > the MLM that nmh-workers uses---I suspect it has one of those fancy
> > features that thinks an email that was sent to one address shouldn't
> > be also sent to another address (i.e. if the
Hi Greg,
> yes, awk and sed are in my repertoire, but, well, i was wondering if i
> could avoid those in this case.
For list's archive's completeness, the nmh way, using mhl(1) as Ken
suggested, is
/usr/lib/nmh/mhl -nomoreproc \
-form <(echo received:compress,nowrap,split) \
On Fri, 22 Nov 2019 20:51:52 +0100, Steffen Nurpmeso said:
> I prefer people using Mail-Followup-To: instead of some ML
> software modifying the address lists, they could as well just
> avoid resending the mail!?! Yes, i mean, well.
> I really like looking into old archives and i hope what i see
>Curiously, the email you sent me appears to have never arrived via the
>MLM that nmh-workers uses---I suspect it has one of those fancy features
>that thinks an email that was sent to one address shouldn't be also sent
>to another address (i.e. if the address of the To/Cc recipient is also a
Andy Bradford wrote in <20191122084003.18170.qmail@angmar.bradfordfamily\
.org>:
|Thus said Steffen Nurpmeso on Thu, 21 Nov 2019 23:14:29 +0100:
|> I have heared someone revived qmail and wants to include some patches
|> for builtin TLS etc. That sounded very much interesting, especially if
Thus said Steffen Nurpmeso on Thu, 21 Nov 2019 23:14:29 +0100:
> I have heared someone revived qmail and wants to include some patches
> for builtin TLS etc. That sounded very much interesting, especially if
> its mailing-list manager would be maintained again!
There has been some momentum
Andy Bradford wrote in <20191121072709.1303.qm...@angmar.bradfordfamily.org>:
|Thus said Greg Minshall on Wed, 20 Nov 2019 10:41:34 +0530:
|> then, i'd like to use something like fmttest(1) to print out all the
|> "Received:" lines in an e-mail message. ideally, each "Received:" line
|>
Thus said Greg Minshall on Wed, 20 Nov 2019 10:41:34 +0530:
> then, i'd like to use something like fmttest(1) to print out all the
> "Received:" lines in an e-mail message. ideally, each "Received:" line
> would come out on a separate line; less ideally, but i'm sure very
> practical, a
greg wrote:
> ps -- the goal is a little "blame" script for e-mail that tells you how
> long a given message spent moving from A to B. (this relies, of course,
> on globally synchronized clocks, but that seems much more likely to be
> true today than it did when Received: lines were first
hi, Valdis!
ah, formail -- awesome! yes, that does great.
Ken and Ralph -- thanks for your replies. yes, awk and sed are in my
repertoire, but, well, i was wondering if i could avoid those in this
case.
cheers, Greg
ps -- the goal is a little "blame" script for e-mail that tells you how
long
On Wed, 20 Nov 2019 10:41:34 +0530, Greg Minshall said:
> hi. i'd like first, of course, to thank you all for nmh!
>
> then, i'd like to use something like fmttest(1) to print out all the
> "Received:" lines in an e-mail message. ideally, each "Received:" line
> would come out on a separate
Hi Paul,
> greg wrote:
> > then, i'd like to use something like fmttest(1) to print out all the
> > "Received:" lines in an e-mail message. ideally, each "Received:"
> > line would come out on a separate line; less ideally, but i'm sure
> > very
>
> Is strict use of only MH tools a requirement
greg wrote:
> then, i'd like to use something like fmttest(1) to print out all the
> "Received:" lines in an e-mail message. ideally, each "Received:" line
> would come out on a separate line; less ideally, but i'm sure very
Is strict use of only MH tools a requirement for some reason?
Hi Greg,
> That's all I've time for at the moment, but others may chip in and this
> saves them covering some of the ground.
Ken's mhl(1) suggestion is what I would have tried. But there's also
non-nmh solutions, e.g. sed or awk if you're familiar with those.
This prints all the Foo fields,
>then, i'd like to use something like fmttest(1) to print out all the
>"Received:" lines in an e-mail message. ideally, each "Received:" line
>would come out on a separate line; less ideally, but i'm sure very
>practical, a very long line would come out, with some odd ascii code
>separating the
Hi Greg,
Keeping you CC'd.
> context: the problem is there are (typically) multiple "Received:"
> header in an e-mail messages; can try either of these
>
> bash% fmttest -outsize max +SOMEFOLDER 660 -format "%(putstr{received});"
> bash% fmttest -outsize max +SOMEFOLDER 660 -format
hi. i'd like first, of course, to thank you all for nmh!
then, i'd like to use something like fmttest(1) to print out all the
"Received:" lines in an e-mail message. ideally, each "Received:" line
would come out on a separate line; less ideally, but i'm sure very
practical, a very long line
24 matches
Mail list logo
