[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Elisp manual: @section Mode Line Format is unclear
From: |
Stephen J. Turnbull |
Subject: |
Re: Elisp manual: @section Mode Line Format is unclear |
Date: |
Fri, 30 Dec 2005 16:02:43 +0900 |
User-agent: |
Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.5-b24 (dandelion, linux) |
>>>>> "Andreas" == Andreas Schwab <address@hidden> writes:
Andreas> What is that if not a definition?
It *is* a definition. What it is not, is *documentation*. Thus the
reference to "specifiers" (an over-elaborated XEmacs API full of YAGNI[1]
violations, whose documentation focuses on what YAGN).
What Alan would like to see, I suppose, is something like:
- Variable: mode-line-format
The value of this variable is a mode-line construct which
describes the mode-line to redisplay.
The simplest form of mode-line construct is a string containing
zero or more %-constructs. A %-construct is a reference to a
variable whose value is to be interpolated into the modeline at
that point. The %-construct is introduced by the character `%',
followed by optional formatting specifications, and terminated by
a single character which indicates the variable whose value is to
be interpolated.
Example: `(setq mode-line-format "%B")' puts the buffer name, and
nothing else, in the mode-line of the current buffer.
A symbol is also a modeline construct. Its value is interpolated
in the
Footnotes:
[1] "You Aren't Gonna Need It", for those who most naturally
interpret "XP" to refer to a proprietary operating system, is one of
the basic ideas of the XP == Extreme Programming style.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.