From 4b1ed1bb560a63bd5e136f2023ab3987a516af42 Mon Sep 17 00:00:00 2001 From: Chong Yidong Date: Sat, 15 Aug 2009 22:02:59 +0000 Subject: [PATCH] * advice.texi (Argument Access in Advice): Note that argument positions are zero-based (Bug#3932). --- doc/lispref/ChangeLog | 3 +++ doc/lispref/advice.texi | 10 +++++----- 2 files changed, 8 insertions(+), 5 deletions(-) diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index 3aab7e3b623..e07386d8b88 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,5 +1,8 @@ 2009-08-15 Chong Yidong + * advice.texi (Argument Access in Advice): Note that argument + positions are zero-based (Bug#3932). + * commands.texi (Distinguish Interactive): Minor copyedit. * display.texi (Face Attributes): Add xref to Displaying Faces for diff --git a/doc/lispref/advice.texi b/doc/lispref/advice.texi index 57cfc616f23..a3669781e0e 100644 --- a/doc/lispref/advice.texi +++ b/doc/lispref/advice.texi @@ -603,11 +603,11 @@ for that function. A more robust method is to use macros that are translated into the proper access forms at activation time, i.e., when constructing the -advised definition. Access macros access actual arguments by position -regardless of how these actual arguments get distributed onto the -argument variables of a function. This is robust because in Emacs Lisp -the meaning of an argument is strictly determined by its position in the -argument list. +advised definition. Access macros access actual arguments by their +(zero-based) position, regardless of how these actual arguments get +distributed onto the argument variables of a function. This is robust +because in Emacs Lisp the meaning of an argument is strictly +determined by its position in the argument list. @defmac ad-get-arg position This returns the actual argument that was supplied at @var{position}. -- 2.39.2