unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Joseph Mingrone <jrm@FreeBSD.org>, notmuch@notmuchmail.org
Subject: Re: Elisp error with recent master-branch Emacs
Date: Sun, 05 Dec 2021 08:26:29 -0400	[thread overview]
Message-ID: <87tufnqlu2.fsf@tethera.net> (raw)
In-Reply-To: <87zgpfritg.fsf@tethera.net>

David Bremner <david@tethera.net> writes:

> Joseph Mingrone <jrm@FreeBSD.org> writes:
>
>> Hello,
>>
>> When building the FreeBSD OS package for notmuch-emacs, we have begun to
>> see build errors recently that report
>>
>>         (error "Unknown button type `help-function'").
>>
>> http://pkg.ftfl.ca/data/12amd64-default/2021-12-04_12h41m25s/logs/errors/notmuch-emacs_devel-0.34.1_1.log
>>
>> This seems to be related to a recent change in the Emacs master branch
>> (Emacs 29).  We build new emacs-devel packages around the 1st and 15th
>> day of each month that pull the latest from the Emacs master branch.
>> This notmuch-emacs breakage started after the Dec. 1 package update for
>> emacs-devel.
>>
>> Regards,
>>
>
> I did manage to duplicate this problem on debian, so I guess it's not
> FreeBSD specific. Not sure how to fix it yet, it looks like there are
> many changes to docstring processing in emacs 29, that may be related.

It turned out to be an emacs bug, fixed (thanks to Lars I.) in commit 

   5404973916dc5d0b92604d31ad7dca2358bc5b9a

If you update to current master in emacs, notmuch should build again (at
least it does for me now).

d

  reply	other threads:[~2021-12-05 12:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-04 20:33 Elisp error with recent master-branch Emacs Joseph Mingrone
2021-12-05  0:34 ` David Bremner
2021-12-05 12:26   ` David Bremner [this message]
2021-12-06  1:55     ` Joseph Mingrone

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://notmuchmail.org/

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

  git send-email \
    --in-reply-to=87tufnqlu2.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=jrm@FreeBSD.org \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).