From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: clear-kill-ring function
Date: Wed, 28 Oct 2015 03:14:55 +0100 [thread overview]
Message-ID: <874mhbagdc.fsf@debian.uxu> (raw)
In-Reply-To: 87lhaof6tm.fsf@skimble.plus.com
Sharon Kimble <boudiccas@skimble.plus.com> writes:
> (defun qdot/clear-kill-ring (interactive)
>
> I'm not sure what you mean or how to show it.
> Is that what you meant?
You put (interactive) after the parameter list (the
argument names), which is empty in your case so should
be the empty list, ().
An interactive function is a "command", which means
you can invoke it from M-x and also bind it to a key.
There are situations where you can have the same
function behave differently when called from Elisp
(i.e., invoked from another piece of code) compared to
when it is used interactively (again, with M-x or
a keystroke bound to that function) - however, as for
me, I don't see a great value in this distinction and
has only rarely used it. Perhaps someone who disagrees
will explain why it is there and what benefits
it brings.
Note that you can invoke non-interactive functions
with `eval-expr' (or `M-:') so it is not like they are
inaccessible to the "interactive" user. (They will
execute noninteractively still, of course.)
--
underground experts united
http://user.it.uu.se/~embe8573
next prev parent reply other threads:[~2015-10-28 2:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1159.1445970298.7904.help-gnu-emacs@gnu.org>
2015-10-27 18:49 ` clear-kill-ring function Barry Margolin
2015-10-27 19:29 ` Sharon Kimble
2015-10-27 20:18 ` Michael Heerdegen
2015-10-28 6:06 ` Sharon Kimble
[not found] ` <mailman.1186.1446012388.7904.help-gnu-emacs@gnu.org>
2015-10-28 10:37 ` Joost Kremers
2015-10-28 12:46 ` Michael Heerdegen
2015-10-29 2:34 ` Emanuel Berg
2015-10-28 2:14 ` Emanuel Berg [this message]
2015-10-27 18:24 Sharon Kimble
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=874mhbagdc.fsf@debian.uxu \
--to=embe8573@student.uu.se \
--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).