From: Michael Heerdegen via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 69573@debbugs.gnu.org
Cc: gabriele@medialab.sissa.it, Andrea Corallo <acorallo@gnu.org>
Subject: bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil)
Date: Thu, 07 Mar 2024 06:55:17 +0100 [thread overview]
Message-ID: <871q8mbn7e.fsf@web.de> (raw)
In-Reply-To: <87r0gmbvnc.fsf@web.de> (Michael Heerdegen via's message of "Thu, 07 Mar 2024 03:52:55 +0100")
Michael Heerdegen via "Bug reports for GNU Emacs, the Swiss army knife
of text editors" <bug-gnu-emacs@gnu.org> writes:
> I can't find a commit "ac89b1141a26" in my repository, though. Where
> does your Emacs come from (is it maybe a modified version)?
Forget this question please. I can now reproduce with master, too.
But: This is only reproducible when I build Emacs with native
compilation enabled. Then I get this backtrace with your recipe:
| Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
| forward-paragraph(1)
| fill-forward-paragraph(1)
| fill-region(11 528 left t)
| easy-mmode--mode-docstring("MWE mode" "Mwe mode" mwe-mode-map mwe-mode nil)
| #f(compiled-function (arg1 arg2 &rest rest) "Define a new minor mode MODE....
| elisp--eval-last-sexp(nil)
When I load the source of paragraphs.el (where `forward-paragraph' is
defined) the problem goes away.
Maybe Andrea can help? Just CC'd - I don't know how to continue here.
Thx,
Michael.
next prev parent reply other threads:[~2024-03-07 5:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 23:53 bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil) Gabriele Nicolardi
2024-03-06 0:31 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-06 5:16 ` Gabriele Nicolardi
2024-03-07 2:52 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-07 5:55 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-03-07 16:26 ` Gabriele Nicolardi
2024-03-09 4:30 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-09 14:47 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-09 21:41 ` Andrea Corallo
2024-03-09 21:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 13:52 ` Andrea Corallo
2024-03-15 14:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-15 16:22 ` Gabriele Nicolardi
2024-03-15 16:58 ` Andrea Corallo
2024-03-17 9:30 ` Gabriele Nicolardi
2024-03-15 17:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-17 9:33 ` Gabriele Nicolardi
2024-03-18 9:35 ` Andrea Corallo
2024-03-18 17:28 ` Gabriele Nicolardi
2024-03-18 19:42 ` Andrea Corallo
2024-03-26 7:34 ` Andrea Corallo
2024-03-09 4:33 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-09 7:14 ` Gabriele Nicolardi
2024-03-06 5:42 ` Gabriele Nicolardi
2024-03-07 3:15 ` Michael Heerdegen 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=871q8mbn7e.fsf@web.de \
--to=bug-gnu-emacs@gnu.org \
--cc=69573@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=gabriele@medialab.sissa.it \
--cc=michael_heerdegen@web.de \
/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).