Gnus development mailing list
 help / color / mirror / Atom feed
From: Raphael Kubo da Costa <kubito@gmail.com>
To: ding@gnus.org
Subject: Re: Using the new auth-source
Date: Fri, 18 Feb 2011 13:47:03 -0200	[thread overview]
Message-ID: <ijm49p$6d9$1@dough.gmane.org> (raw)
In-Reply-To: <ijlo61$ap$1@dough.gmane.org>

Raphael Kubo da Costa wrote:

> Katsumi Yamaoka wrote:
> 
>> Raphael Kubo da Costa <kubito@gmail.com> wrote:
>>> I get the following warnings when byte-compiling Gnus:
>> 
>>> In auth-source-search:
>>> auth-source.el:581:39:Warning: reference to free variable `backend'
>>> auth-source.el:567:31:Warning: assignment to free variable `backend'
>> 
>> Mee too.  I'm not sure of it but this seems to solve the problem:
>> 
>> --- auth-source.el~	2011-02-18 01:46:05.637646083 +0000
>> +++ auth-source.el	2011-02-18 12:09:34.784606979 +0000
>> @@ -511,5 +511,5 @@
>>                       collect (nth i spec)))
>>           (found (auth-source-recall spec))
>> -         filtered-backends accessor-key found-here goal matches)
>> +         backend filtered-backends accessor-key found-here goal matches)
>>  
>>      (if (and found auth-source-do-cache)
> 
> I can confirm it solves the warnings ant the error I was getting. Now I
> get the following error when starting Gnus:
> 
> Unable to open server nnimap+Personal due to: Wrong type argument: (or
> eieio-object-p class-p), nil

OK, so the problems seems to be here (in auth-source-search):

      ;; If we didn't find anything, then we allow the backend(s) to                                                                                                                                         
      ;; create the entries.                                                                                                                                                                                 
      (when (and create
                 (not matches))
        (let ((match (apply
                      (slot-value backend 'search-function)
                      :backend backend
                      :create create
                      :delete delete
                      spec)))
          (when match
            (push (list backend match) matches))))

`backend' should probably be referenced inside a loop (such as the `dolist' 
loop before the code I've pasted). OTOH, if I do enclose the `let' call in a 
(dolist backend filtered-backends), I am prompted twice for the same data 
here (I'm finally able to connect to the IMAP server, though).




  reply	other threads:[~2011-02-18 15:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 22:53 Lars Ingebrigtsen
2011-02-17 23:06 ` Lars Ingebrigtsen
2011-02-17 23:46   ` Lars Ingebrigtsen
2011-02-18 10:49     ` Steinar Bang
2011-02-18 11:59     ` Raphael Kubo da Costa
2011-02-18 12:12       ` Katsumi Yamaoka
2011-02-18 12:20         ` Raphael Kubo da Costa
2011-02-18 15:47           ` Raphael Kubo da Costa [this message]
2011-02-18 22:09             ` Lars Ingebrigtsen
2011-02-18 20:22     ` Ted Zlatanov
2011-02-18  9:05 ` Steinar Bang

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='ijm49p$6d9$1@dough.gmane.org' \
    --to=kubito@gmail.com \
    --cc=ding@gnus.org \
    /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).