Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: Paul Jarc <prj@po.cwru.edu>, <ding@gnus.org>
Subject: Re: Strange server names confusion
Date: Mon, 03 Sep 2001 16:17:45 +0200	[thread overview]
Message-ID: <vafd7582wae.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0109031022190.12206-100000@lie.extundo.com> (Simon Josefsson's message of "Mon, 3 Sep 2001 10:23:12 +0200 (CEST)")

Simon Josefsson <jas@extundo.com> writes:

> Don't forget `gnus-method-equal', `gnus-methods-equal-p' etc.  `eq' should
> probably not be used for comparing methods, I think.

Maybe so.  But if the two are eq, how can it happen that Gnus behaves
differently?!?

But maybe Gnus uses gnus-method-equal directly on the two strings?
Hm.  Anyway:

/----
| *** Welcome to IELM ***  Type (describe-mode) for help.
| ELISP> (gnus-method-equal "quimby" "nntp:quimby")
| nil
| ELISP> (gnus-methods-equal-p "quimby" "nntp:quimby")
| *** Eval error ***  Wrong type argument: listp, "quimby"
| ELISP> 
\----

I'm not sure what this means.  But I observe:

/----
| ELISP> (gnus-server-equal "quimby" "nntp:quimby")
| t
\----

Fascinating.

kai
-- 
Symbol's function definition is void: signature


  reply	other threads:[~2001-09-03 14:17 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 [this message]
2001-09-03 23:04               ` Paul Jarc
2001-09-04 13:44                 ` Kai Großjohann
2001-09-05  0:55                   ` Paul Jarc
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=vafd7582wae.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --cc=ding@gnus.org \
    --cc=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).