Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Major splitting problem ... Advice please
Date: Thu, 11 Oct 2001 11:54:02 -0400	[thread overview]
Message-ID: <m3eloa2mvj.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vxkr8sa8jw3.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "Thu, 11 Oct 2001 08:02:20 -0400")

Karl Kleinpaste <karl@charcoal.com> wrote:
> It's too bad that xargs(1) can't be used following the grep; the inner
> "while" loop could be disposed of entirely if so, but that's not how
> mv(1) works.

xargs -n1 should work.

> function newmv()
> {
>   destdir=$1
>   shift
>   mv "$@" $destdir
> }
>
> Then the "while" is replaced by
>      grep -isl ... | xargs newmv $newdir
> which perhaps isn't all that icky after all.

Assuming you make newmv a shell script and not just a shell function
in the current shell.

>> Also the problem of some messages that
>> came late to a thread, landing in a different group arises.  Keeping
>> all thead members in one group may not even be possible, except by
>> hand.  I'm not sure. 
>
> As soon as you decide to use date-based storage, you break either that
> storage mechanism or you break border-crossing threads.  Pick one or
> the other.

Yes... but if you could choose the date boundaries on the fly, you
could get whole threads for all the threads you're interested in.
Is there anything that can do this?


paul



  reply	other threads:[~2001-10-11 15:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-11  5:26 Harry Putnam
2001-10-11  7:40 ` Kai Großjohann
2001-10-12  4:01   ` Harry Putnam
2001-10-11 12:02 ` Karl Kleinpaste
2001-10-11 15:54   ` Paul Jarc [this message]
2001-10-11 16:25     ` Paul Jarc
2001-10-11 16:37       ` Kai Großjohann
2001-10-12 16:44 ` Rob Browning
2001-10-13  4:28   ` Harry Putnam

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3eloa2mvj.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).