Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: Error with latest Gnus
Date: Tue, 06 May 2003 07:30:08 -0500	[thread overview]
Message-ID: <un0i0qmun.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <87of2gwdo6.fsf@goliathbbs.dnsalias.net>

Joerg Jaspert <joerg@ganneff.de> writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>>> Debugger entered--Lisp error: (invalid-function (macro lambda (group) "Find the real name of a foreign newsgroup." (\` (let ((gname (\, group))) (if (string-match "^[^:]+:" gname) (substring gname (match-end 0)) gname)))))
>>>   gnus-group-real-name("nnimap+mail:INBOX.Mailinglisten.LWN")
>>>   #[nil "..." [gnus-newsgroup-name in-debian-devel-announce-group-p string-match "debian.devel.announce" gnus-group-real-name] 4]()
>>>   run-hooks(gnus-select-article-hook)
>>>   apply(run-hooks gnus-select-article-hook)
>>>   (save-current-buffer (apply (quote run-hooks) funcs))
>>>   gnus-run-hooks(gnus-select-article-hook)
>>>   gnus-summary-display-article(216 nil)
>>>   gnus-summary-select-article(nil nil pseudo)
>>>   gnus-summary-scroll-up(1)
>>>   call-interactively(gnus-summary-scroll-up)
>> Well, gnus-group-real-name worked here using the group that you
>> provided.
>
> It doesnt matter in which group, its everywhere.
>
>> The debug message also looks rather bizarre so let's assume that the
>> problem is in the byte-compiled file.  Try deleting, or at least
>> renaming, the gnus-util.elc file so that the gnus-util.el file will be
>> loaded.  That should either give you a better error message or fix the
>> problem.  If it is the later, you'll want to recompile gnus-util.el.
>
> Sorry, i should have written that. This is without byte-compile. With a
> byte-compiled file you cant really read/understand the error message.
>
> I already tried it without any .elc from Gnus. No difference. :()

What does (macroexpand '(gnus-group-real-name
"nnimap+mail:INBOX.Mailinglisten.LWN")) return?

You might also try (progn (debug) (gnus-group-real-name
"nnimap+mail:INBOX.Mailinglisten.LWN")) so that you can step into the
macro expansion.  That can be fairly ugly but this may be an expansion
error rather than an evaluation error.

Kevin



  reply	other threads:[~2003-05-06 12:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-05 12:21 Joerg Jaspert
2003-05-06  6:52 ` Kevin Greiner
2003-05-06 10:51   ` Joerg Jaspert
2003-05-06 12:30     ` Kevin Greiner [this message]
2003-05-06 13:21       ` Joerg Jaspert
2003-05-06 15:24         ` Kevin Greiner
2003-05-06 18:37           ` Joerg Jaspert
2003-05-06 12:07   ` Robert Epprecht
2003-05-06 12:23     ` Kevin Greiner
2003-05-06 13:02       ` Reiner Steib
2003-05-08 22:48         ` Dave Love
2003-05-08 22:47 ` Dave Love

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=un0i0qmun.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.com \
    /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).