Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <>
Subject: Re: problem with (display . [not expire]) with git emacs
Date: Thu, 01 Feb 2024 14:29:34 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Dan Christensen <> writes:

> Two additional things.  First, I should have said that Gnus does not
> raise an error.  It just silently ignores my [not expire] setting.
> Second, here is a link to the relevant commit, which shows the diff:
> Is anyone else using git emacs since Nov 29 and also using (display
> . [not expire])?

I just tried it out, and actually got a popup buffer with the "Malformed
function" error you mentioned in your first message.

Looks like the culprit is effectively this:

  `(lambda ()
    ,(cdr (assoc 'expire gnus-summary-display-cache))))

That's pretty much what `gnus-category-make-function' is doing, given
that at that point `gnus-category-predicate-alist' has been let-bound to
the value of `gnus-summary-display-cache'. I don't see where that
variable gets all its values, but one of its elements is:

(expire . #f(compiled-function () #<bytecode 0xc27be483>))

And apparently that's what is barfing when it gets byte compiled.
Weirdly, after fooling around with it a bit, the bytecode there must
have gotten "fixed" somehow, and the display parameter stopped giving me
an error (and started working correctly). Dunno what's happening there.


  reply	other threads:[~2024-02-01 23:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 20:10 Dan Christensen
2024-01-31 23:41 ` Dan Christensen
2024-02-01 22:29   ` Eric Abrahamsen [this message]
2024-02-02 14:58     ` Dan Christensen
2024-02-05 13:47       ` Dan Christensen
2024-02-05 15:18         ` Eric Abrahamsen
2024-02-01 22:33   ` Eric Abrahamsen

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).