From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 68931@debbugs.gnu.org
Subject: bug#68931: 30.0.50; Gnus byte-compilation error with (display . [not expire]) with git emacs
Date: Wed, 21 Feb 2024 14:05:56 -0800 [thread overview]
Message-ID: <875xyhjwvv.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87zfvtehx8.fsf@uwo.ca> (Dan Christensen's message of "Wed, 21 Feb 2024 14:28:03 -0500")
Dan Christensen <jdc@uwo.ca> writes:
> On Feb 5, 2024, Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> wrote:
>
>> 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
>> @@ -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
>
> I see that this part was committed and then reverted. I just manually
> applied it to master, and it makes the warnings in the *Compile-Log*
> buffer go away, and my display predicate still works correctly. The
> warnings said:
>
> Warning: Use ‘funcall’ instead of ‘#[0 \301\300!\207 [expire
> gnus-article-marked-p] 2]’ in the function position
>
> So I recommend that this be committed again.
It will be! I only reverted because I'd committed completely by
accident, and Stefan had mentioned it might need some equivalent
adjustments elsewhere to be completely correct. I just haven't tested it
fully yet.
next prev parent reply other threads:[~2024-02-21 22:05 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
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 [this message]
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=875xyhjwvv.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=68931@debbugs.gnu.org \
/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).