On Fri, 16 Feb 2007 22:59:22 -0500
Bill Sconce <[EMAIL PROTECTED]> wrote:
> Feb 9, 2007
>
> To All Radio Amateurs...
> >From the Hosstraders, Joe K1RQG, Bob W1GWU, and Norm W1ITT
I overlooked the real discussion! (I was working from an
announcement I saw in the ham radio press.) Maddog, who d
On 2/17/07, Bill Sconce <[EMAIL PROTECTED]> wrote:
Since each message is a file in mh-land, this command:
grep -in "hosstrad" ~/Mail/...gnhlug.x/* | less
yields one line from each of the files (messages, headers included)
which have "Hosstraders" in them.
Shouldn't it yield *every* line wh
>>grep -in "hosstrad" ~/Mail/...gnhlug.x/*
>
>Perhaps the shell did not expand the file names in dated order
You're right about that, but that would only be part of the
problem; MH msgs are stored in files with simple numeric names
like 1, 2, 423, , etc, but although the numeric ordering
of
Bill Sconce writes:
> Before I posted I looked to see if anyone had already done so...
> I searched my GNHLUG folder (mh!) for earlier posts on the subject.
> Since each message is a file in mh-land, this command:
> grep -in "hosstrad" ~/Mail/...gnhlug.x/* | less
> yields one line from each
The number of arguments that you can pass to a program (for example,
grep) is finite. Also know that getconf(ARG_MAX) is a byte-count and
not an argument count.
A situation for which xargs may sometimes be useful, it depends on
what you're trying to do.
--DTVZ
_
On Tuesday, Feb 20th 2007 at 11:16 -0500, quoth Drew Van Zandt:
=>> The number of arguments that you can pass to a program (for example,
=>> grep) is finite. Also know that getconf(ARG_MAX) is a byte-count and
=>> not an argument count.
=>
=>A situation for which xargs may sometimes be useful, it
> From: [EMAIL PROTECTED] (Kevin D. Clark)
> Date: Tue, 20 Feb 2007 10:46:01 -0500
> Another thing that you might want to consider is that the grep command
> that you present could die in a mysterious way -- you might have too
> much mail in a given folder, and thus you might have too many
> argu
>xargs, specified with both -s and -n, should never fail this way:
>
> $ find $spec -print0 | xargs --null -s $s -n $n $command
>
>for appropriate values of $s and $n.
Depending on circumstances, dramatic speedups can result from
judicious use of -l, thus:
find $spec -print0 | xargs -
On Sun, 18 Feb 2007 10:05:43 -0500
"Michael ODonnell" <[EMAIL PROTECTED]> wrote:
> On Sat, 17 Feb 2007 17:18:41 -0500
> "Ben Scott" <[EMAIL PROTECTED]> wrote:
> > Shouldn't
> > [grep -in "hosstrad" ~/Mail/...gnhlug.x/*]
> > yield *every* line which has "Hosstraders" in it?
> > -i = ca
>Tip: there were LOTS of files, each one with a filename of a
>string of decimal digits, the values of which grew by +1 with
>each successive message as it arrived (and they had not been
>sorted or renamed). For instance, the messages bridging New
>Year's 2006 were:
>
On 2/18/07, Bill Sconce <[EMAIL PROTECTED]> wrote:
P.S. The prize has yet to be awarded. Ben's explanation is close,
but his wording (including that "perhaps") makes me hold out for
one or two details.
Well, I'm not really familiar with MH in practice; I've read a FAQ
and a web page or two, i
What an anaylsis. Correct in every respect, pointing out one
possibility after another, concluding (correctly) that one after
another wasn't the problem...
On Sun, 18 Feb 2007 19:44:59 -0500
"Ben Scott" <[EMAIL PROTECTED]> wrote:
> ...your "grep" command should certainly find all the messages..
12 matches
Mail list logo
