From: "Mattias Engdegård" <mattias.engdegard@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Dan Christensen <jdc@uwo.ca>,
68931@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#68931: 30.0.50; Gnus byte-compilation error with (display . [not expire]) with git emacs
Date: Mon, 5 Feb 2024 15:00:36 +0100 [thread overview]
Message-ID: <523B7DE4-EA66-4686-845A-35CDCC575F92@gmail.com> (raw)
In-Reply-To: <86r0hr13eu.fsf@gnu.org>
>> Debugger entered--returning value: "Malformed function ‘#[0 \"\\301\\300!\\207\" [expire gnus-article-marked-p] 2]’"
...
>> * gnus-summary-display-make-predicate((not expire))
Apparently, gnus-category-make-function-1 creates code that isn't really valid Lisp but that we have previously allowed anyway: (F ...) where F is a (non-symbol) function value, instead of using `funcall`.
We could (and probably should) allow this for compatibility but perhaps it's time to at least start warning about it? It makes the quirky semantics of a Lisp-2 even quirkier.
next prev parent reply other threads:[~2024-02-05 14: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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=523B7DE4-EA66-4686-845A-35CDCC575F92@gmail.com \
--to=mattias.engdegard@gmail.com \
--cc=68931@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jdc@uwo.ca \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.