diff options
| -rw-r--r-- | doc/lispref/ChangeLog | 4 | ||||
| -rw-r--r-- | doc/lispref/display.texi | 12 |
2 files changed, 11 insertions, 5 deletions
diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog index 39ed20c3f88..fc2580385f4 100644 --- a/doc/lispref/ChangeLog +++ b/doc/lispref/ChangeLog @@ -1,3 +1,7 @@ +2014-01-07 Glenn Morris <rgm@gnu.org> + + * display.texi (Logging Messages): Copyedits re messages-buffer. + 2014-01-06 Paul Eggert <eggert@cs.ucla.edu> Specify .texi encoding (Bug#16292). diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi index be8db83396c..8236742ae2c 100644 --- a/doc/lispref/display.texi +++ b/doc/lispref/display.texi @@ -478,13 +478,15 @@ this macro this way: Almost all the messages displayed in the echo area are also recorded in the @file{*Messages*} buffer so that the user can refer back to them. This includes all the messages that are output with -@code{message}. This buffer is read-only and has the major-mode -@code{messages-buffer-mode}. The best way to retrieve that buffer is -the function @code{messages-buffer}. +@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}. @defun messages-buffer -Return the @file{*Messages*} buffer. -If it does not exist, create and it switch it to @code{messages-buffer-mode}. +This function returns the @file{*Messages*} buffer. If it does not +exist, it creates it, and switches it to @code{messages-buffer-mode}. @end defun @defopt message-log-max |