(Function Safety): Use inforef instead of pxref for SES.

diff --git a/lispref/ChangeLog b/lispref/ChangeLog
index 5c2f7398aca2689c58e365813ae5d195a41de513..fa271dcf506891fbd8144f4a1c6e04caa6cf9c7f 100644 (file)
--- a/lispref/ChangeLog
+++ b/lispref/ChangeLog
@@ -1,3 +1,11 @@
+2003-10-23  Luc Teirlinck  <teirllm@auburn.edu>
+
+       * display.texi (Temporary Displays): Add xref to `Documentation
+       Tips'.
+
+       * functions.texi (Function Safety): Use inforef instead of pxref
+       for SES.
+
 2003-10-23  Andreas Schwab  <schwab@suse.de>
 
        * Makefile.in (TEX, texinputdir): Don't define.

diff --git a/lispref/functions.texi b/lispref/functions.texi
index 14279d4dab2ecf367e006e020f7d56b7ef678d6c..4ee101ca87130d610459b33cd727abe0ac030096 100644 (file)
--- a/lispref/functions.texi
+++ b/lispref/functions.texi
@@ -1187,12 +1187,12 @@ following the definition, just like macros.
 @cindex function safety
 @cindex safety of functions
 
-Some major modes such as SES (@pxref{Top,,,ses}) call functions that
-are stored in user files.  User files sometimes have poor
-pedigrees---you can get a spreadsheet from someone you've just met, or
-you can get one through email from someone you've never met.  So it is
-risky to call a function whose source code is stored in a user file
-until you have determined that it is safe.
+Some major modes such as SES call functions that are stored in user
+files.  (@inforef{Top, ,ses}, for more information on SES.)  User
+files sometimes have poor pedigrees---you can get a spreadsheet from
+someone you've just met, or you can get one through email from someone
+you've never met.  So it is risky to call a function whose source code
+is stored in a user file until you have determined that it is safe.
 
 @defun unsafep form &optional unsafep-vars
 Returns @code{nil} if @var{form} is a @dfn{safe} Lisp expression, or