Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Epprecht <epprecht@sunweb.ch>
Subject: Wizards, Saints and Guardian Angels
Date: 09 May 2001 14:03:21 +0200	[thread overview]
Message-ID: <86vgnahgqe.fsf@i2d.home> (raw)

In the thread about Lars' message <m3n19jsrfo.fsf@quimbies.gnus.org>
'A road map for Oort Gnus' there has been a lot of discussion about
setup wizards (or saints) and the like.  I would suggest thinking
about creating yet another type of helpers in the Gnus universe:
The Guardian Angels.

Let me give an actual example that just bites me to show what I mean:
My ISP's news server is very unreliable. Not only that it breaks down
much too often, just to come back with message numbers in a completely
changed range, but also my ISP was sold three times to another company.
The news server was always aliased (hope the word make sense here) to
another news server without prior notice.  Can you imagine the mess
in my (agentized) Gnus after such events?  It would have been very
helpful, if Gnus would have stopped, saying that the received data
looks strange and asked if I want to proceed or what, before changing
it's internal data.  I could have made a fresh backup first or so...

Would it be possible to recognise some of the more frequent error
conditions *before* they could damage Gnus' data?  What are the
most frequent encountered such conditions that do confuse Gnus?


I see four stages where such Guardian Angels could make the live
of a naive Gnus user like me more convenient:

* Warn the user before corrupted incoming data would damage Gnus' files
  where possible.  (This being Gnus it would be switch able of course).
* Warn the user when internal data seems corrupted.
* Giving more information in the manual about disaster diagnosis and
  recovery (see next point).
* Providing more helper functions to (check and) fix things.

While setup wizards would help just once in the career of a Gnus
user, things like this could help him out every now and then.

Maybe it would also be possible to make Gnus even more robust
than it already is in such a harsh environment.  What do you think?

Robert Epprecht


             reply	other threads:[~2001-05-09 12:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-09 12:03 Robert Epprecht [this message]
2001-05-09 21:39 ` Christoph Conrad

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=86vgnahgqe.fsf@i2d.home \
    --to=epprecht@sunweb.ch \
    /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).