From 2a7e072e5396d00c17b7d2a12ce867138f6f8c19 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Sat, 31 Dec 2022 10:44:53 +0200 Subject: [PATCH] ; Fix documentation of 'defalias' * doc/lispref/functions.texi (Defining Functions): Document that a defalias's DEFINITION can be a macro. (Bug#60432) --- doc/lispref/functions.texi | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi index 9d5a2661916..9232dc38e78 100644 --- a/doc/lispref/functions.texi +++ b/doc/lispref/functions.texi @@ -700,7 +700,7 @@ redefinition from unintentional redefinition. @defun defalias name definition &optional doc @anchor{Definition of defalias} This function defines the symbol @var{name} as a function, with -definition @var{definition} (which can be any valid Lisp function). +definition @var{definition} (which can be any valid Lisp function or macro). Its return value is @emph{undefined}. If @var{doc} is non-@code{nil}, it becomes the function documentation @@ -713,10 +713,10 @@ If @var{name} has a @code{defalias-fset-function} property, however, the associated value is used as a function to call in place of @code{fset}. The proper place to use @code{defalias} is where a specific function -name is being defined---especially where that name appears explicitly in -the source file being loaded. This is because @code{defalias} records -which file defined the function, just like @code{defun} -(@pxref{Unloading}). +or macro name is being defined---especially where that name appears +explicitly in the source file being loaded. This is because +@code{defalias} records which file defined the function, just like +@code{defun} (@pxref{Unloading}). By contrast, in programs that manipulate function definitions for other purposes, it is better to use @code{fset}, which does not keep such -- 2.39.2