From: Derrell.Lipman@UnwiredUniverse.com
Cc: ding@gnus.org
Subject: Re: Create groups after moving nnml dirs?
Date: Fri, 03 Jan 2003 12:57:53 -0500 [thread overview]
Message-ID: <65t686am.fsf@random.localnet.unwireduniverse.com> (raw)
In-Reply-To: <84el7uazy6.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Fri, 03 Jan 2003 18:46:41 +0100")
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> Say I do "tar cfpj x.tbz Mail/foo" on one machine and then unpack it
> on another machine. How do I tell Gnus about the new groups foo.bar
> and foo.quux?
>
> And I don't mean manually. Actually, we're talking about more than
> 1,000 groups. It's not fun to type G m for each of those!
How about something like this:
M-x shell
cd foo
ls -1
<copy result list to *scratch*>
C-x b *scratch* RET
M-<
C-x (
C-SPC
C-E
M-w
C-x b *Group* RET
G w foo.C-Y RET
C-x b *scratch* RET
C-a C-n
C-x )
C-u 10000 C-x e
Derrell
next prev parent reply other threads:[~2003-01-03 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 17:46 Kai Großjohann
2003-01-03 17:57 ` Derrell.Lipman [this message]
2003-01-03 18:17 ` Kai Großjohann
2003-01-03 20:19 ` Lars Magne Ingebrigtsen
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=65t686am.fsf@random.localnet.unwireduniverse.com \
--to=derrell.lipman@unwireduniverse.com \
--cc=ding@gnus.org \
/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).