From: Joost Kremers <joostkremers@fastmail.fm>
To: Christopher Dimech <dimech@gmx.com>
Cc: help-gnu-emacs@gnu.org, moasenwood@zoho.eu
Subject: Re: Define interactive function with arguments
Date: Fri, 09 Oct 2020 11:22:30 +0200 [thread overview]
Message-ID: <87d01r92jt.fsf@fastmail.fm> (raw)
In-Reply-To: <trinity-984e2b18-a840-4ce1-8b9d-de0fc3ab0098-1602233844970@3c-app-mailcom-bs09>
On Fri, Oct 09 2020, Christopher Dimech wrote:
> Your comment simply means, look at the manual and look at the
> code
> and don't bother me. Nobody forced you to reply, and if people
> do
> not want to advise, they can simply disregard me. Have heard
> such
> talk all the time, especially in industry.
I'm truly sorry if it came across wrong, but I didn't mean my
comment that way. It was meant in a "help someone help themself"
kind of way. The Emacs Lisp Intro is a very helpful resource (I
think) and I didn't see anyone point it out yet. (Though I may of course have
missed it, in which case I apologise.)
In the spirit of helpfulness, these two sections of the Elisp
Intro answer your specific question:
https://www.gnu.org/software/emacs/manual/html_node/eintr/Interactive.html#Interactive
and:
https://www.gnu.org/software/emacs/manual/html_node/eintr/Interactive-Options.html#Interactive-Options
--
Joost Kremers
Life has its moments
next prev parent reply other threads:[~2020-10-09 9:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 23:15 Define interactive function with arguments Christopher Dimech
2020-10-08 23:41 ` Stefan Monnier
2020-10-08 23:47 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-09 6:38 ` Christopher Dimech
2020-10-09 7:18 ` Joost Kremers
2020-10-09 8:57 ` Christopher Dimech
2020-10-09 9:22 ` Joost Kremers [this message]
2020-10-09 9:52 ` Christopher Dimech
2020-10-09 14:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-09 14:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-09 14:24 ` Christopher Dimech
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=87d01r92jt.fsf@fastmail.fm \
--to=joostkremers@fastmail.fm \
--cc=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).