From f2027cdf5adf8bcb620a31addf5a5851e542affd Mon Sep 17 00:00:00 2001 From: Lars Magne Ingebrigtsen Date: Thu, 14 Jul 2011 02:02:09 +0200 Subject: [PATCH] (Documentation Basics): Add a link to the Function Documentation node. Fixes: debbugs:6580 --- doc/lispref/ChangeLog | 5 +++++ doc/lispref/help.texi | 11 ++++++----- 2 files changed, 11 insertions(+), 5 deletions(-) diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index 3e40384eec7..19da0a3c442 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,8 @@ +2011-07-14 Lars Magne Ingebrigtsen + + * help.texi (Documentation Basics): Add a link to the Function + Documentation node (bug#6580). + 2011-07-13 Lars Magne Ingebrigtsen * keymaps.texi (Menu Bar): Mention :visible and :enable diff --git a/doc/lispref/help.texi b/doc/lispref/help.texi index 63fc06c929b..0ce05d55a07 100644 --- a/doc/lispref/help.texi +++ b/doc/lispref/help.texi @@ -78,11 +78,12 @@ function or variable that it describes: @item @kindex function-documentation The documentation for a function is usually stored in the function -definition itself (@pxref{Lambda Expressions}). The function -@code{documentation} knows how to extract it. You can also put -function documentation in the @code{function-documentation} property -of the function name. That is useful with definitions such as -keyboard macros that can't hold a documentation string. +definition itself (@pxref{Lambda Expressions} and @pxref{Function +Documentation}). The function @code{documentation} knows how to +extract it. You can also put function documentation in the +@code{function-documentation} property of the function name. That is +useful with definitions such as keyboard macros that can't hold a +documentation string. @item @kindex variable-documentation -- 2.39.2