Gnus development mailing list
 help / color / mirror / Atom feed
From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Strange server names confusion
Date: Tue, 04 Sep 2001 20:55:05 -0400	[thread overview]
Message-ID: <m31ylm8ni8.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <vafitez9ik5.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 04 Sep 2001 15:44:42 +0200")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
> So maybe the Gnus source should be searched for rogue occurrences of
> gnus-method-equal and gnus-methods-equal-p (what's the difference?).

Well, one is a function, and one is a macro, though it's not clear
why.  gnus-methods-equal-p considers (nnchoke "foo") to be equal to
(nnchoke "foo" (param value)) if nnchoke uses 'address in
gnus-declare-backend.  If it doesn't, then all nnchoke methods are
equal for g-m-e-p.  For gnus-method-equal, two methods are equal when
they have the same backend and following list elements are equal, but
in a possibly different order.  g-m-e-p also interprets nil arguments
as gnus-select-method, unlike g-m-e.

> I'm guessing that Gnus should use gnus-server-equal in most places.
> What do you think?

I'd like it if Gnus were less tolerant of sloppiness.  Then it'd be
harder for users to make a mess of their configurations.  So if a list
is found where a string is expected (or vice versa), there should be a
nice error message telling the user how to fix the problem.


paul


  reply	other threads:[~2001-09-05  0:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-01 19:06 Kai Großjohann
2001-09-01 19:39 ` Simon Josefsson
2001-09-01 21:59   ` Kai Großjohann
2001-09-02  4:54     ` Paul Jarc
2001-09-02 10:44       ` Kai Großjohann
2001-09-02 23:13         ` Paul Jarc
2001-09-03  8:23           ` Simon Josefsson
2001-09-03 14:17             ` Kai Großjohann
2001-09-03 23:04               ` Paul Jarc
2001-09-04 13:44                 ` Kai Großjohann
2001-09-05  0:55                   ` Paul Jarc [this message]
2001-09-04  0:05             ` Paul Jarc
2001-09-03 10:21           ` Kai Großjohann

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=m31ylm8ni8.fsf@multivac.cwru.edu \
    --to=prj@po.cwru.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).