Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Impossible to edebug stuff that calls auth-source?
Date: Tue, 22 Feb 2011 11:42:52 -0600	[thread overview]
Message-ID: <87d3mkynhf.fsf@lifelogs.com> (raw)
In-Reply-To: <87ei71q6b0.fsf@gnus.org>

On Mon, 21 Feb 2011 16:08:51 -0800 Lars Ingebrigtsen <larsi@gnus.org> wrote: 

LI> Andreas Schwab <schwab@linux-m68k.org> writes:
>> defclass probably needs a debug declaration (*Note (elisp) Instrumenting
>> Macro Calls::).

LI> I haven't actually asked edebug to instrument any of the auth-source
LI> functions, just functions that eventually lead to auth-source being
LI> called, so edebug shouldn't know about that stuff anyway, should it?
LI> *scratches head*

You got me.  I don't use edebug, only (debug) calls, the printf of
ELisp.  I keep meaning to learn edebug but haven't had the time.

Ted




  reply	other threads:[~2011-02-22 17:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 23:19 Lars Ingebrigtsen
2011-02-21 23:57 ` Andreas Schwab
2011-02-22  0:08   ` Lars Ingebrigtsen
2011-02-22 17:42     ` Ted Zlatanov [this message]
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=87d3mkynhf.fsf@lifelogs.com \
    --to=tzz@lifelogs.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).