From 0a85d12474e6551581bcf87de9129359c0f8c233 Mon Sep 17 00:00:00 2001 From: Eli Zaretskii Date: Mon, 27 Nov 2017 18:24:29 +0200 Subject: [PATCH] Fix ELisp "Warning Tips" * doc/lispref/tips.texi (Warning Tips): Clarify when to use 'require' wrapped by 'eval-when-compile'. (Bug#29462) --- doc/lispref/tips.texi | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi index 17fd4a1027e..42a68677f58 100644 --- a/doc/lispref/tips.texi +++ b/doc/lispref/tips.texi @@ -534,9 +534,17 @@ that you know @emph{will} be defined, use a @code{declare-function} statement (@pxref{Declaring Functions}). @item -If you use many functions and variables from a certain file, you can -add a @code{require} for that package to avoid compilation warnings -for them. For instance, +If you use many functions, macros, and variables from a certain file, +you can add a @code{require} (@pxref{Named Features, require}) for +that package to avoid compilation warnings for them, like this: + +@example +(require 'foo) +@end example + +@noindent +If you need only macros from some file, you can require it only at +compile time (@pxref{Eval During Compile}). For instance, @example (eval-when-compile -- 2.39.5