emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] /srv/bzr/emacs/emacs-23 r100328: More fallout from fixing


From: Eli Zaretskii
Subject: [Emacs-diffs] /srv/bzr/emacs/emacs-23 r100328: More fallout from fixing bug #7587.
Date: Sat, 25 Dec 2010 12:14:48 +0200
User-agent: Bazaar (2.0.3)

------------------------------------------------------------
revno: 100328
committer: Eli Zaretskii <address@hidden>
branch nick: emacs-23
timestamp: Sat 2010-12-25 12:14:48 +0200
message:
  More fallout from fixing bug #7587.
  
   src/xdisp.c (Fformat_mode_line): Doc fix: no need to state that only
   the basic faces are supported.
   doc/lispref/modes.texi (Emulating Mode Line): Fix last change.
   etc/NEWS: Remove the entry about format-mode-line accepting only
   basic faces.
modified:
  doc/lispref/ChangeLog
  doc/lispref/modes.texi
  etc/NEWS
  src/ChangeLog
  src/xdisp.c
=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2010-12-18 08:53:28 +0000
+++ b/doc/lispref/ChangeLog     2010-12-25 10:14:48 +0000
@@ -1,3 +1,7 @@
+2010-12-25  Eli Zaretskii  <address@hidden>
+
+       * modes.texi (Emulating Mode Line): Fix last change.
+
 2010-12-18  Eli Zaretskii  <address@hidden>
 
        * modes.texi (Emulating Mode Line): Update documentation of

=== modified file 'doc/lispref/modes.texi'
--- a/doc/lispref/modes.texi    2010-12-18 08:53:28 +0000
+++ b/doc/lispref/modes.texi    2010-12-25 10:14:48 +0000
@@ -2119,22 +2119,17 @@
 buffer.
 
 The value string normally has text properties that correspond to the
-faces, keymaps, etc., that the mode line would have.  And any character
-for which no @code{face} property is specified gets a default value
-determined by @var{face}.  If @var{face} is @code{t}, that stands for
-either @code{mode-line} if @var{window} is selected, otherwise
address@hidden  If @var{face} is @code{nil} or omitted, that
-stands for no face property.
-
-However, if @var{face} is an integer, the value has no text properties.
+faces, keymaps, etc., that the mode line would have.  Any character for
+which no @code{face} property is specified by @var{format} gets a
+default value determined by @var{face}.  If @var{face} is @code{t}, that
+stands for either @code{mode-line} if @var{window} is selected,
+otherwise @code{mode-line-inactive}.  If @var{face} is @code{nil} or
+omitted, that stands for the default face.  If @var{face} is an integer,
+the value returned by this function will have no text properties.
 
 You can also specify other valid faces as the value of @var{face}.
-If the value is a @dfn{basic face}, one of @code{default}, @code{mode-line},
address@hidden, @code{header-line}, or @code{tool-bar}, that
-face provides the @code{face} property for characters whose face is not
-specified by @var{format}.  Any other face is treated as @code{default},
-but you can remap one of the basic faces (@pxref{Face Remapping}) to get
-the same effect as with non-basic faces.
+If specified, that face provides the @code{face} property for characters
+whose face is not specified by @var{format}.
 
 Note that using @code{mode-line}, @code{mode-line-inactive}, or
 @code{header-line} as @var{face} will actually redisplay the mode line

=== modified file 'etc/NEWS'
--- a/etc/NEWS  2010-12-24 11:21:26 +0000
+++ b/etc/NEWS  2010-12-25 10:14:48 +0000
@@ -1866,11 +1866,6 @@
 ** `mode-name' is no longer guaranteed to be a string.
 Use `(format-mode-line mode-name)' to ensure a string value.
 
-** `format-mode-line' now supports only a few basic faces as its FACE argument.
-The FACE argument to `format-mode-line' should be one of `default',
-`mode-line', `mode-line-inactive', `header-line', or `tool-bar'.  Any
-other face is treated as `default'.
-
 ** The function x-font-family-list has been removed.
 Use the new function font-family-list (see Lisp Changes, below).
 

=== modified file 'src/ChangeLog'
--- a/src/ChangeLog     2010-12-24 10:14:44 +0000
+++ b/src/ChangeLog     2010-12-25 10:14:48 +0000
@@ -1,3 +1,8 @@
+2010-12-25  Eli Zaretskii  <address@hidden>
+
+       * xdisp.c (Fformat_mode_line): Doc fix: no need to state that only
+       the basic faces are supported.
+
 2010-12-24  Jan Djärv  <address@hidden>
 
        * xterm.c (x_check_fullscreen): Fix pixel/character mixup.

=== modified file 'src/xdisp.c'
--- a/src/xdisp.c       2010-12-17 15:38:37 +0000
+++ b/src/xdisp.c       2010-12-25 10:14:48 +0000
@@ -17883,17 +17883,19 @@
 First arg FORMAT specifies the mode line format (see `mode-line-format'
 for details) to use.
 
+By default, the format is evaluated for the currently selected window.
+
 Optional second arg FACE specifies the face property to put on all
 characters for which no face is specified.  The value nil means the
 default face.  The value t means whatever face the window's mode line
-currently uses \(either `mode-line' or `mode-line-inactive',
-depending).  An integer value means the value string has no text
-properties.  Otherwise, the value should be one of `default',
-`mode-line', `mode-line-inactive', `header-line', or `tool-bar'.
+currently uses (either `mode-line' or `mode-line-inactive',
+depending on whether the window is the selected window or not).
+An integer value means the value string has no text
+properties.
 
 Optional third and fourth args WINDOW and BUFFER specify the window
 and buffer to use as the context for the formatting (defaults
-are the selected window and the window's buffer).  */)
+are the selected window and the WINDOW's buffer).  */)
      (format, face, window, buffer)
      Lisp_Object format, face, window, buffer;
 {


reply via email to

[Prev in Thread] Current Thread [Next in Thread]