From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Ability to use a button to run interactive function
Date: Mon, 28 Aug 2023 16:45:15 +0200 [thread overview]
Message-ID: <87bkerql8k.fsf@dataswamp.org> (raw)
In-Reply-To: wdySivXR4uYwIxQjpf3UqHn_DT4bDe741f1ZRekMtKw4o7MBPjEP4SVsiKTZK7Kb0OwfGsStHuBoxgn-G3fLK_dV-U6JlMUQgyycYSoshKU=@protonmail.com
Heime wrote:
> The following function does not allow me to call it via
> a button.
If we are talking buttons as in keys on a keyboard, they the
answer is you didn't bind the button to the function.
> Would this be possible, whilst also be allowed to call the
> function interactively using 'M-x maces-snapshot' ?
It is already callable like that since it is interactive (a
command).
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-08-28 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 14:34 Ability to use a button to run interactive function Heime
2023-08-28 14:45 ` Emanuel Berg [this message]
2023-08-28 14:55 ` Stephen Berman
2023-08-28 16:33 ` Heime
2023-08-28 20:02 ` Stephen Berman
2023-08-28 15:28 ` Marcin Borkowski
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=87bkerql8k.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=help-gnu-emacs@gnu.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.
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).