Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Abrahams <dave@boostpro.com>
To: ding@gnus.org
Subject: Re: No such function: nnregistry-request-group
Date: Thu, 29 Sep 2011 08:34:33 -0400	[thread overview]
Message-ID: <m2k48rbk86.fsf@pluto.luannocracy.com> (raw)
In-Reply-To: <87oby3n46f.fsf@lifelogs.com>


on Thu Sep 29 2011, Ted Zlatanov <tzz-AT-lifelogs.com> wrote:

> On Wed, 28 Sep 2011 20:25:34 -0400 Dave Abrahams <dave@boostpro.com> wrote: 
>
> DA> Can anyone tell me what this means?
> DA> Debugger entered--Lisp error: (error "No such function: nnregistry-request-group")
> DA>   signal(error ("No such function: nnregistry-request-group"))
> DA>   error("No such function: %s" nnregistry-request-group)
> DA>   gnus-request-group("nndoc+4E821BF6.3070409@boostpro.com-ephemeral:4E821BF6.3070409@boostpro.com" t)
> DA>   gnus-check-group-server()
> DA>   gnus-request-article-this-buffer(-2
> DA> "nndoc+4E821BF6.3070409@boostpro.com-ephemeral:4E821BF6.3070409@boostpro.com")
> DA>   gnus-article-prepare(-2 nil)
> DA>   gnus-summary-display-article(-2 nil)
> DA>   gnus-summary-select-article(nil nil pseudo)
> DA>   gnus-summary-scroll-up(1)
> DA>   call-interactively(gnus-summary-scroll-up nil nil)
>
> nnregistry.el doesn't define that function.  I'm pretty sure you're not
> supposed to ask it for group info.

As you can probably see from the backtrace, I'm not the one doing the
asking.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com




  reply	other threads:[~2011-09-29 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-29  0:25 Dave Abrahams
2011-09-29  8:28 ` Ted Zlatanov
2011-09-29 12:34   ` Dave Abrahams [this message]
2011-09-29 14:04     ` Ted Zlatanov
2011-09-29 18:59       ` Dave Abrahams
2011-10-06 21:25       ` Lars Magne Ingebrigtsen
2011-10-06 22:27         ` Dave Abrahams

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=m2k48rbk86.fsf@pluto.luannocracy.com \
    --to=dave@boostpro.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).