From 49c650714b9b5601a85f91e4a26c532cb816fcc1 Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Tue, 26 Apr 2005 11:00:56 +0000 Subject: [PATCH] Fix previous change. --- lisp/emacs-lisp/eldoc.el | 2 +- lispref/variables.texi | 7 +++---- 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/lisp/emacs-lisp/eldoc.el b/lisp/emacs-lisp/eldoc.el index 29167c70812..b23217151e3 100644 --- a/lisp/emacs-lisp/eldoc.el +++ b/lisp/emacs-lisp/eldoc.el @@ -45,7 +45,7 @@ ;; Major modes for other languages may use Eldoc by defining an ;; appropriate function as the buffer-local value of -;; `eldoc-print-current-symbol-info-function'. +;; `eldoc-documentation-function'. ;;; Code: diff --git a/lispref/variables.texi b/lispref/variables.texi index b39c4abb719..43f590503ec 100644 --- a/lispref/variables.texi +++ b/lispref/variables.texi @@ -1722,10 +1722,9 @@ stage in the future. @defmac make-obsolete-variable variable new &optional when This macro makes the byte-compiler warn that the variable @var{variable} is obsolete. If @var{new} is a symbol, it is the -variable's new name; the warning messages say to use @var{new} -instead of @var{variable}. -If @var{new} is a string, this is the message and there is no -replacement variable. +variable's new name; then the warning messages says to use @var{new} +instead of @var{variable}. If @var{new} is a string, this is the +message and there is no replacement variable. If provided, @var{when} should be a string indicating when the variable was first made obsolete---for example, a date or a release -- 2.39.2