unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>, akrl@sdf.org
Cc: 50968@debbugs.gnu.org, dfussner@googlemail.com
Subject: bug#50968: 28.0.60; curly quote in lisp form in docstrings
Date: Sun, 03 Oct 2021 14:01:00 +0300	[thread overview]
Message-ID: <831r529xub.fsf@gnu.org> (raw)
In-Reply-To: <87o886sb5e.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun,  03 Oct 2021 11:36:13 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sun, 03 Oct 2021 11:36:13 +0200
> Cc: 50968@debbugs.gnu.org
> 
> David Fussner <dfussner@googlemail.com> writes:
> 
> > To check whether the minor mode is enabled in the current buffer,
> > evaluate ‘(default-value ’show-paren-mode)’.
> >
> > -- end quotation --
> >
> > The straight quote inside the form has become curly (unless gmail has
> > mangled it), preventing evaluation. This part of the docstring comes
> > from a template in
> > easy-mmode.el, so versions of it appear everywhere.
> 
> Yup, this should now be fixed in Emacs 28 (but requires recompiling all
> files that use easy-mmode).

I 'touch'ed all the *.el files that use define-minor-mode, but then
rebuilding Emacs with native-compilation fails with error messages
that complain about frame-XXX.eln:

    ELC+ELN  ../lisp/international/mule-cmds.elc
  emacs: can't find function "F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_41" in compilation unit d:\gnu\git\emacs\native-comp\src\../native-lisp/28.0.60-bc5f6bd2/preloaded/frame-b40fc590-734bdcac.eln
  Makefile:286: recipe for target `../lisp/international/mule-cmds.elc' failed

I saw others report similar problems recently.

I worked around this by removing emacs and bootstrap-emacs executables
(and the corresponding pdmp files), which causes a re-dump.

There were no such problems in the build without native-compilation.

frame.el was one of the 'touch'ed files, so it was recompiled, and it
sounds like the problem is with some discrepancy between the old
frame-XXX.eln file with which emacs was dumped, and the new one?  And
it's somehow triggered by refreshing the preloaded *.eln files that
were meanwhile recompiled?

Andrea, what do these error messages mean, and how to avoid them in
the future?  Do we lack some cleanup or some prerequisites in our
Makefile's?





  reply	other threads:[~2021-10-03 11:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-02 14:14 bug#50968: 28.0.60; curly quote in lisp form in docstrings David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-03  9:36 ` Lars Ingebrigtsen
2021-10-03 11:01   ` Eli Zaretskii [this message]
2021-10-03 13:42     ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=831r529xub.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50968@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=dfussner@googlemail.com \
    --cc=larsi@gnus.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).