From 4ac594cd846d2750ac85d0f7edff775d5f5a363d Mon Sep 17 00:00:00 2001 From: "Richard M. Stallman" Date: Mon, 27 Dec 2004 16:58:07 +0000 Subject: [PATCH] (Emulating Mode Line): Document format's BUFFER arg. --- lispref/modes.texi | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/lispref/modes.texi b/lispref/modes.texi index 01958873d33..2abb8a9c0d9 100644 --- a/lispref/modes.texi +++ b/lispref/modes.texi @@ -1736,7 +1736,7 @@ It is normally @code{nil}, so that ordinary buffers have no header line. the text that would appear in a mode line or header line based on certain mode-line specification. -@defun format-mode-line &optional format window no-props +@defun format-mode-line &optional format window no-props buffer This function formats a line of text according to @var{format} as if it were generating the mode line for @var{window}, but instead of displaying the text in the mode line or the header line, it returns @@ -1752,6 +1752,8 @@ The argument @var{window} defaults to the selected window. The value string normally has text properties that correspond to the faces, keymaps, etc., that the mode line would have. If @var{no-props} is non-@code{nil}, the value has no text properties. +If @var{buffer} is non-@code{nil}, all the information used is taken +from @var{buffer}; by default,it comes from @var{window}'s buffer. @end defun @node Imenu -- 2.39.2