From: Soren Dayton <csdayton@cs.uchicago.edu>
Cc: ding@gnus.org
Subject: Re: Proposal/Request for feature for splitting to FQ groups
Date: 02 Jul 1999 18:43:37 -0500 [thread overview]
Message-ID: <xcdwvwibot2.fsf@sloohah.cs.uchicago.edu> (raw)
In-Reply-To: wmperry@aventail.com's message of "01 Jul 1999 15:33:44 -0500"
wmperry@aventail.com (William M. Perry) writes:
> Soren Dayton <csdayton@cs.uchicago.edu> writes:
>
> > So I was playing with splitting again (this is a hobby of mine) and I
> > would really like to be able to split from my nnml backend into an nnimap
> > mailbox. This would be really, really nice for me.
>
> Ooooh oooh me too!
>
> Please please please?!?!?! :)
>
> I volunteer lots of beer if this gets into pgnus before it gets a 'real'
> number and we don't add any more features. 'GCC' can do this kind of
> thing, so why not the splitting code? :)
So, I've thought about it some more, and there may be good reasons `why
not the splitting code'. I don't see a good failure behavior. What
happens if the method cannot be brought up (it is on a down file server,
the imap server isn't up, I just deleted the directory that stores the
messages for that method, etc.).
For Gcc, it's easy because it's the user's problem. Gnus beeps at me,
and I go fix it or change it or whatever.
But if I've been on vacation for a month, I start up gnus, and go take a
shower (after all, bbdb splitting ain't fast) and it starts splitting.
And my imap server (which I am splitting messages into) is down. I'm
screwed. Stick it somewhere where I have to split 500 messages by hand?
Not me. Stick it in the crash box? Eep.
What would the right behavior be here?
Soren
next prev parent reply other threads:[~1999-07-02 23:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-01 19:29 Soren Dayton
1999-07-01 20:33 ` William M. Perry
1999-07-02 23:43 ` Soren Dayton [this message]
1999-07-02 19:54 ` William M. Perry
1999-07-04 4:36 ` Lars Magne Ingebrigtsen
1999-07-04 20:01 ` Kai.Grossjohann
1999-07-05 4:49 ` Lars Magne Ingebrigtsen
1999-07-05 9:46 ` Kai.Grossjohann
1999-07-06 4:16 ` 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=xcdwvwibot2.fsf@sloohah.cs.uchicago.edu \
--to=csdayton@cs.uchicago.edu \
--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).