Gnus development mailing list
 help / color / mirror / Atom feed
From: "Rene H. Larsen" <rhl@traceroute.dk>
Subject: Re: Unable to create Dejanews nnweb groups
Date: 01 Dec 1999 20:38:44 +0100	[thread overview]
Message-ID: <87zovutprv.fsf@worldonline.dk> (raw)
In-Reply-To: <m3so1mpxaz.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> "Rene H. Larsen" <rhl@traceroute.dk> writes:
> 
> > What if Gnus were to first try the current method, and if that fails,
> > ask (y-or-n-p) if it should try DejaNews.  This could be customizable
> > by setting gnus-article-refer-try-dejanews to 'always, 'never, or
> > 'ask, e.g.
> 
> Hm.  I'm not much of a fan of queries, really.  I think people should
> just customize this to do what they want.

I can certainly sympathise with that in the general case.  The reason
I was looking for a way to make Gnus query whether to try Deja is that
I have an intermittent Internet connection, and there is no easy way
to tell if the Internet connection is up.  I don't want Gnus to try
and contact Deja when the connection is down, but I would like to have
the option to do so when the connection is up.

I did try mocking around with gnus-refer-article-method, and using the
example from the Info documentation, namely

     (setq gnus-refer-article-method
           '(current
             (nnweb "refer" (nnweb-type dejanews))))

does not seem to work correctly.  Pressing ^ on an article whose
parent is still present on the server works correctly.  However, if I
press ^ on an article whose parent has expired, XEmacs complains:

  Cannot open load file: current

The backtrace is:

  signal(file-error ("Cannot open load file" "current"))
  load("current" nil t nil)
  require(current)
  gnus-server-opened((current (nnweb "refer" (nnweb-type dejanews))))
  gnus-check-group-server()
  gnus-request-article-this-buffer(-4 "dk.edb.system.unix.hardware")
  gnus-article-prepare(-4 nil)
  gnus-summary-display-article(-4 nil)
  gnus-summary-goto-article(-4 nil t)
  gnus-summary-refer-article("<syvK3.1969$et6.51290@news010.image.dk>")
  gnus-summary-refer-parent-article(1)
  call-interactively(gnus-summary-refer-parent-article)

This is with a CVS pgnus as of ten minutes ago.
-- 
Echelon bait:
supercomputer Nazi AK-47 Bosnia Croatian Uzi SCUD missile Legion of
Doom White Water Marxist Ron Brown smuggle Craig Livingstone Project
Monarch quiche


  reply	other threads:[~1999-12-01 19:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-09 16:01 Hannu Koivisto
1999-11-10  8:10 ` Steinar Bang
1999-11-11 14:03   ` Lars Magne Ingebrigtsen
1999-11-11 14:50     ` Steinar Bang
1999-11-12  7:07       ` Lars Magne Ingebrigtsen
1999-11-12  8:23         ` Lars Magne Ingebrigtsen
1999-11-12 17:59           ` Per Abrahamsen
1999-11-16  9:11             ` Lars Magne Ingebrigtsen
1999-11-16 14:34               ` Rene H. Larsen
1999-12-01 14:09                 ` Lars Magne Ingebrigtsen
1999-12-01 19:38                   ` Rene H. Larsen [this message]
1999-12-06  3:58                     ` Lars Magne Ingebrigtsen
1999-11-13  1:01         ` Hannu Koivisto
1999-12-01 14:08           ` 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=87zovutprv.fsf@worldonline.dk \
    --to=rhl@traceroute.dk \
    /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).