add symbolic color name syntax support into the command color.
This commit is contained in:
parent
191c0eea0a
commit
4e769ee998
5 changed files with 165 additions and 54 deletions
15
ChangeLog
15
ChangeLog
|
@ -1,3 +1,18 @@
|
|||
1999-10-13 OKUJI Yoshinori <okuji@kuicr.kyoto-u.ac.jp>
|
||||
|
||||
* stage2/builtins.c (color_func): Do not set NORMAL_COLOR or
|
||||
HIGHLIGHT_COLOR directly, but use NEW_NORMAL_COLOR and
|
||||
NEW_HIGHLIGHT_COLOR as temporary storages instead.
|
||||
New internal function `color_number' is used to convert a
|
||||
symbolic color representation into a color number.
|
||||
Try color_number at first, and if fails, then try
|
||||
safe_parse_maxint for each of NORMAL and HIGHLIGHT.
|
||||
(builtin_color): The long doc does not describe the raw number
|
||||
syntax but the symbolic color name syntax.
|
||||
* docs/grub.texi (Commands): Adjusted to the long doc of
|
||||
BUILTIN_COLOR.
|
||||
* docs/menu.lst: Add examples of "fallback" and "color".
|
||||
|
||||
1999-10-13 OKUJI Yoshinori <okuji@kuicr.kyoto-u.ac.jp>
|
||||
|
||||
* stage2/char_io.c [!STAGE1_5] (get_cmdline): If C is a newline
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue