summaryrefslogtreecommitdiff
path: root/lispref/variables.texi
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>1995-10-09 19:39:45 +0000
committerRichard M. Stallman <rms@gnu.org>1995-10-09 19:39:45 +0000
commitab4b18358fa636b07dd0fa88d54a2f8d89ef0079 (patch)
treef36d80805581df8700923694c2a4879abd7e7b3a /lispref/variables.texi
parentb1c7e43439f490bbc186a2f0137fc450819a9ea0 (diff)
downloademacs-ab4b18358fa636b07dd0fa88d54a2f8d89ef0079.tar.gz
Explain when to use make-variable-buffer-local.
Diffstat (limited to 'lispref/variables.texi')
-rw-r--r--lispref/variables.texi9
1 files changed, 9 insertions, 0 deletions
diff --git a/lispref/variables.texi b/lispref/variables.texi
index c3bd61541d8..22813ea5b63 100644
--- a/lispref/variables.texi
+++ b/lispref/variables.texi
@@ -1213,6 +1213,15 @@ buffer-local, so that any subsequent attempt to set it will make it
local to the current buffer at the time.
The value returned is @var{variable}.
+
+@strong{Note:} It is a mistake to use @code{make-variable-buffer-local}
+for user-option variables, simply because users @emph{might} want to
+customize them differently in different buffers. Users can make any
+variable local, when they wish to.
+
+The main use of @code{make-variable-buffer-local} is when a variable is
+used for internal purposes, and the Lisp program depends on having
+separate values in separate buffers.
@end deffn
@defun local-variable-p variable &optional buffer