From 82ba818ff456bcd6d56a06226e3f27e98fbb55c3 Mon Sep 17 00:00:00 2001 From: Craig Jennings Date: Thu, 14 Aug 2025 22:58:58 -0500 Subject: removing all downloaded devdocs files --- devdocs/elisp/defining-commands.html | 31 ------------------------------- 1 file changed, 31 deletions(-) delete mode 100644 devdocs/elisp/defining-commands.html (limited to 'devdocs/elisp/defining-commands.html') diff --git a/devdocs/elisp/defining-commands.html b/devdocs/elisp/defining-commands.html deleted file mode 100644 index 773e8f59..00000000 --- a/devdocs/elisp/defining-commands.html +++ /dev/null @@ -1,31 +0,0 @@ -

Defining Commands

The special form interactive turns a Lisp function into a command. The interactive form must be located at top-level in the function body, usually as the first form in the body; this applies to both lambda expressions (see Lambda Expressions) and defun forms (see Defining Functions). This form does nothing during the actual execution of the function; its presence serves as a flag, telling the Emacs command loop that the function can be called interactively. The argument of the interactive form specifies how the arguments for an interactive call should be read.

Alternatively, an interactive form may be specified in a function symbol’s interactive-form property. A non-nil value for this property takes precedence over any interactive form in the function body itself. This feature is seldom used.

Sometimes, a function is only intended to be called interactively, never directly from Lisp. In that case, give the function a non-nil interactive-only property, either directly or via declare (see Declare Form). This causes the byte compiler to warn if the command is called from Lisp. The output of describe-function will include similar information. The value of the property can be: a string, which the byte-compiler will use directly in its warning (it should end with a period, and not start with a capital, e.g., "use (system-name) instead."); t; any other symbol, which should be an alternative function to use in Lisp code.

Generic functions (see Generic Functions) cannot be turned into commands by adding the interactive form to them.

- - - - - - - - - - - - - - - - - - - -
• Using Interactive - General rules for interactive.
• Interactive Codes - The standard letter-codes for reading arguments in various ways.
• Interactive Examples - Examples of how to read interactive arguments.
• Command Modes - Specifying that commands are for a specific mode.
• Generic Commands - Select among command alternatives.
-

- Copyright © 1990-1996, 1998-2022 Free Software Foundation, Inc.
Licensed under the GNU GPL license.
- https://www.gnu.org/software/emacs/manual/html_node/elisp/Defining-Commands.html -

-
-- cgit v1.2.3