Gnus development mailing list
 help / color / mirror / Atom feed
From: Mark Plaksin <happy@usg.edu>
Subject: Re: PATCH: Make nnrss fail gracefully when it can't fetch a feed
Date: Sat, 31 Dec 2005 10:49:47 -0500	[thread overview]
Message-ID: <87zmmhfeqs.fsf@stone.tss.usg.edu> (raw)
In-Reply-To: <b4mzmmtdw50.fsf@jpl.org>

Katsumi Yamaoka <yamaoka@jpl.org> writes:

>>>>>> In <87r785nsu6.fsf@stone.tss.usg.edu>
>>>>>>	Mark Plaksin <happy@usg.edu> wrote:
>
>> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>
>>>> -	  (mm-url-insert url)))
>>>> +          (condition-case nil
>>>> +              (mm-url-insert url)
>>>> +            (error (nnheader-message 3 "nnrss: Failed to fetch %s" url)))))
>>>
>>> Isn't it better to use just `message' since it is obviously an
>>> error?  And also (sit-for N) might be required.
>
> I meant we can use `message' instead of `nnheader-message' there
> as the following:
>
> (condition-case nil
>     (mm-url-insert url)
>   (error (message "nnrss: Failed to fetch %s" url)))
>
> I never said that we should use `error' instead of
> `nnheader-message'.

OK, I misread or misunderstood.  `message' sounds good to me!

mm-url-insert is also called in nnrss-insert-w3.  I guess there should be a
condition-case there too but I don't understand what nnrss-insert-w3 is for.




  reply	other threads:[~2005-12-31 15:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 17:57 Mark Plaksin
2005-12-21 18:28 ` Mark Plaksin
2005-12-22  3:38 ` Katsumi Yamaoka
2005-12-22 13:50   ` Mark Plaksin
2005-12-22 14:49     ` Katsumi Yamaoka
2005-12-31 15:49       ` Mark Plaksin [this message]
2006-01-01  6:46         ` Katsumi Yamaoka

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=87zmmhfeqs.fsf@stone.tss.usg.edu \
    --to=happy@usg.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).