unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: jdc@uwo.ca, 68931@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#68931: 30.0.50; Gnus byte-compilation error with (display . [not expire]) with git emacs
Date: Mon, 05 Feb 2024 16:32:10 +0200	[thread overview]
Message-ID: <86jznj0yol.fsf@gnu.org> (raw)
In-Reply-To: <523B7DE4-EA66-4686-845A-35CDCC575F92@gmail.com> (message from Mattias Engdegård on Mon, 5 Feb 2024 15:00:36 +0100)

> From: Mattias Engdegård <mattias.engdegard@gmail.com>
> Date: Mon, 5 Feb 2024 15:00:36 +0100
> Cc: Dan Christensen <jdc@uwo.ca>,
>  68931@debbugs.gnu.org,
>  Stefan Monnier <monnier@iro.umontreal.ca>
> 
> >> 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.

I think the offending function should be fixed not to produce invalid
code, rather than support such code.





  reply	other threads:[~2024-02-05 14:32 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 [this message]
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

  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=86jznj0yol.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=68931@debbugs.gnu.org \
    --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).