From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Impossible to edebug stuff that calls auth-source?
Date: Mon, 21 Feb 2011 15:19:31 -0800 [thread overview]
Message-ID: <87vd0dkmbg.fsf@gnus.org> (raw)
I'm always edebugging a lot, and last night it failed mysteriously with
this message at seemingly odd, by reproducible points:
Wrong type argument: arrayp, auth-source-backend
I drilled down to try to see what's going on, and I think the culprit is
auth-source, somehow.
If I edebug `nntp-send-authinfo', for instance, it will fail with that
error message when it reaches this point:
(nth 0 (auth-source-search :max 1
;; TODO: allow the virtual server name too
:host nntp-address
:port '("119" "nntp"))))
I haven't looked any further down what's going on. Does the EIEIO stuff
make edebug bug out? Or something?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next reply other threads:[~2011-02-21 23:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 23:19 Lars Ingebrigtsen [this message]
2011-02-21 23:57 ` Andreas Schwab
2011-02-22 0:08 ` Lars Ingebrigtsen
2011-02-22 17:42 ` Ted Zlatanov
2011-02-23 8:25 ` Lars Ingebrigtsen
2011-03-16 16:36 ` Ted Zlatanov
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=87vd0dkmbg.fsf@gnus.org \
--to=larsi@gnus.org \
--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).