From 17109647e9d35847b14c5cbe5efffcd747346d89 Mon Sep 17 00:00:00 2001 From: Glenn Morris Date: Mon, 6 Jan 2014 23:50:29 -0800 Subject: [PATCH] Minor tweak for earlier display.texi change --- doc/lispref/display.texi | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi index 8236742ae2c..880ba837ba1 100644 --- a/doc/lispref/display.texi +++ b/doc/lispref/display.texi @@ -481,8 +481,9 @@ them. This includes all the messages that are output with @code{message}. By default, this buffer is read-only and uses the major mode @code{messages-buffer-mode}. Nothing prevents the user from killing the @file{*Messages*} buffer, but the next display of a message -recreates it. Any Lisp code that needs to ensure the @file{*Messages*} -buffer exists should use the function @code{messages-buffer}. +recreates it. Any Lisp code that needs to access the +@file{*Messages*} buffer directly and wants to ensure that it exists +exists should use the function @code{messages-buffer}. @defun messages-buffer This function returns the @file{*Messages*} buffer. If it does not -- 2.39.2