From: goncholden <goncholden@protonmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Adding functionality to a minor mode
Date: Mon, 07 Feb 2022 22:15:31 +0000 [thread overview]
Message-ID: <B5HvO67uSj_UKTyekzx4-xu5dSAvfOEUh4Osu72-NF46ydITBohFL80uKMVsYE14chziEsbFdsQn7RNJO-f4BVcovuhJhaWdtV7plBr6IjU=@protonmail.com> (raw)
In-Reply-To: <87ee4ez76h.fsf@web.de>
------- Original Message -------
On Monday, February 7th, 2022 at 9:40 PM, Michael Heerdegen <michael_heerdegen@web.de> wrote:
> goncholden goncholden@protonmail.com writes:
>
> > > M-: (macroexpand-1 '(define-minor-mode rich-minor-mode ...)) RET to see
> > >
> > > the macroexpanded code of your definition - helps in understanding.
> > >
> > > Debugger entered--Lisp error: (wrong-type-argument stringp \.\.\.)
>
> You should of course macroexpand your complete definition, not the one I abbreviated.
>
> Michael.
I would have to copy the whole function on the minibuffer. Is there an easier way to call macroexpand on rich-minor-mode?
next prev parent reply other threads:[~2022-02-07 22:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 10:00 Adding functionality to a minor mode goncholden via Users list for the GNU Emacs text editor
2022-02-05 18:50 ` goncholden
2022-02-07 0:09 ` goncholden
2022-02-07 6:00 ` Eric Abrahamsen
2022-02-07 13:56 ` goncholden
2022-02-07 18:05 ` Michael Heerdegen
2022-02-07 19:18 ` goncholden
2022-02-07 20:26 ` [External] : " Drew Adams
2022-02-07 20:38 ` goncholden
2022-02-07 20:59 ` Drew Adams
2022-02-07 21:40 ` Michael Heerdegen
2022-02-07 22:15 ` goncholden [this message]
2022-02-07 22:26 ` Michael Heerdegen
2022-02-08 7:41 ` Kevin Vigouroux via Users list for the GNU Emacs text editor
2022-02-08 13:27 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-02-08 17:05 ` goncholden
2022-02-08 22:47 ` goncholden
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='B5HvO67uSj_UKTyekzx4-xu5dSAvfOEUh4Osu72-NF46ydITBohFL80uKMVsYE14chziEsbFdsQn7RNJO-f4BVcovuhJhaWdtV7plBr6IjU=@protonmail.com' \
--to=goncholden@protonmail.com \
--cc=help-gnu-emacs@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.
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).