[Top][All Lists]

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

Re: [Nmh-workers] [PATCH] scan message numbers from stdin

From: Simon Burge
Subject: Re: [Nmh-workers] [PATCH] scan message numbers from stdin
Date: Tue, 19 Aug 2008 16:18:04 +1000

Eric Gillespie wrote:

> We'll see.  I'll start with show; do you have any other commands
> in mind?  I'm just not feeling foo | refile; I don't see any way
> it's better than refile `foo`, unlike scan and show, where you
> want to see immediate output.

One obvious case with `foo` is where the output of foo will exceed the
argv space available.  For that case, "foo | refile -" would still work,
but then "foo | xargs refile" would too.  This probably isn't a problem
today for any reasonable OS but I'm still scarred by Ultrix's 20kB
ARG_MAX (and the silly app we use to use that needed > 10k of that just
for environment variables).

I'm not sure what I think of the original idea yet..  Harald's example
of using this instead of "pick last:n" seems most useful, but at least
for the way I use "pick last:n" for varying "n" I'd find something like
"pick -reverse whatever | scan -" more useful, where pick started at the
end of the message range.  I'm usually interested in the most recent
message that matches.


reply via email to

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