procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* doc/lispref/display.texi (Logging Messages): Copyedits re messages-buffer.

Browse source
This commit is contained in:
Glenn Morris 2014-01-06 21:56:17 -05:00
parent 9a00bed56f
commit 809d2ce4cf
2 changed files with 11 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
doc/lispref/ChangeLog
View file

@ -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).

12
doc/lispref/display.texi
View file

@ -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