From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: 68931@debbugs.gnu.org, "Eli Zaretskii" <eliz@gnu.org>,
jdc@uwo.ca, "Mattias Engdegård" <mattias.engdegard@gmail.com>
Subject: bug#68931: 30.0.50; Gnus byte-compilation error with (display . [not expire]) with git emacs
Date: Mon, 05 Feb 2024 12:00:42 -0500 [thread overview]
Message-ID: <jwva5oeyhuf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87fry63ojy.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 05 Feb 2024 07:42:41 -0800")
> For my information: the problem here is that
> `gnus-category-make-function' runs `gnus-byte-compile' on a form like
> this:
BTW, `gnus-category-make-function` is a misnomer since it does not
return a function.
> (lambda nil (not (#f(compiled-function () #<bytecode 0x1980ad44c232>))))
>
> And the extra parens around (#f(compiled-function...)) are not strictly legal?
A Lisp function call has the form (FUN . ARGS) where FUN is not expected
to be a function *value* but rather should be a function name (and we
also tolerate a lambda expression, which is a function's source code).
The patch below should fix the core of the problem, but it probably
requires corresponding adjustments in `gnus-function-implies-unread-1`
and `gnus-category-make-function`.
Stefan
diff --git a/lisp/gnus/gnus-agent.el b/lisp/gnus/gnus-agent.el
index 604eea4c33d..cfcbea2e233 100644
--- a/lisp/gnus/gnus-agent.el
+++ b/lisp/gnus/gnus-agent.el
@@ -2911,13 +2911,9 @@
(car func)
(gnus-byte-compile `(lambda () ,func)))))
-(defun gnus-agent-true ()
- "Return t."
- t)
+(defalias 'gnus-agent-true #'always)
-(defun gnus-agent-false ()
- "Return nil."
- nil)
+(defalias 'gnus-agent-false #'ignore)
(defun gnus-category-make-function-1 (predicate)
"Make a function from PREDICATE."
@@ -2925,8 +2921,9 @@ gnus-category-make-function-1
;; Functions are just returned as is.
((or (symbolp predicate)
(functionp predicate))
- `(,(or (cdr (assq predicate gnus-category-predicate-alist))
- predicate)))
+ (let ((fun (or (cdr (assq predicate gnus-category-predicate-alist))
+ predicate)))
+ (if (symbolp fun) `(,fun) `(funcall ',fun))))
;; More complex predicate.
((consp predicate)
`(,(cond
next prev parent reply other threads:[~2024-02-05 17:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 22:11 bug#68931: 30.0.50; Gnus byte-compilation error with (display . [not expire]) with git emacs Dan Christensen
2024-02-05 12:50 ` Eli Zaretskii
2024-02-05 14:00 ` Mattias Engdegård
2024-02-05 14:32 ` Eli Zaretskii
2024-02-05 15:42 ` Eric Abrahamsen
2024-02-05 17:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-02-06 20:42 ` Eric Abrahamsen
2024-02-06 20:46 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-06 21:08 ` Eric Abrahamsen
2024-02-21 19:28 ` Dan Christensen
2024-02-21 22:05 ` Eric Abrahamsen
2024-03-03 2:30 ` Eric Abrahamsen
2024-02-05 14:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-05 17:13 ` Mattias Engdegård
2024-02-05 17:23 ` Dan Christensen
2024-02-05 19:12 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwva5oeyhuf.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=68931@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=jdc@uwo.ca \
--cc=mattias.engdegard@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).