all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Gabriele Nicolardi <gabriele@medialab.sissa.it>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 69573@debbugs.gnu.org
Subject: bug#69573: Eager macro-expansion failure: (wrong-type-argument integer-or-marker-p nil)
Date: Wed, 6 Mar 2024 06:42:48 +0100	[thread overview]
Message-ID: <1a656d80-9cc3-4f31-8e40-b0d903d08986@medialab.sissa.it> (raw)
In-Reply-To: <875xy0qjzf.fsf@web.de>

This is the backtrace in 29.2:

Debugger entered--Lisp error: (error "Eager macro-expansion failure: 
(wrong-type-argumen...")
   error("Eager macro-expansion failure: %S" (wrong-type-argument 
integer-or-marker-p nil))
   internal-macroexpand-for-load((define-minor-mode mwe-mode "MWE mode" 
:init-value nil :lighter (:eval (propertize " MWE " 'face '(:foreground 
"RoyalBlue" :background "DarkGoldenrod1"))) :keymap `((,(kbd "<C-kp-1>") 
. mwe-function)) (if mwe-mode (easy-menu-define mwe-menu mwe-mode-map 
"MWE" '("MWE mode" :visible (not (eq ... ...)) ["mwe-function-1" 
mwe-function-1 :help "mwe-function 1"])) t)) nil)
   eval-buffer()  ; Reading at buffer position 767

Il 06/03/24 01:31, Michael Heerdegen ha scritto:
> Gabriele Nicolardi <gabriele@medialab.sissa.it> writes:
>
>> I have this code: [...]
> I can't reproduce this is with master or 29.1, but I can with 28.2.
> This is the backtrace in 28.2:
>
> Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
>    forward-paragraph(1)
>    fill-forward-paragraph(1)
>    fill-region(1 520 left t)
>    easy-mmode--mode-docstring("MWE mode" "Mwe mode" mwe-mode-map mwe-mode)
>
> I guess you hit a bug that has already been fixed.
>
> Michael.





  parent reply	other threads:[~2024-03-06  5:42 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=1a656d80-9cc3-4f31-8e40-b0d903d08986@medialab.sissa.it \
    --to=gabriele@medialab.sissa.it \
    --cc=69573@debbugs.gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.