All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] colored menu
Date: Mon, 24 Dec 2007 20:46:29 +0100	[thread overview]
Message-ID: <200712242046.29638.okuji@enbug.org> (raw)
In-Reply-To: <20071223210936.GA27776@thorin>

On Sunday 23 December 2007 22:09, Robert Millan wrote:
> This patch adds a nice looking colored menu like the one you'd obtain on
> GRUB Legacy with "color cyan/blue white/blue" command.  Screenshot is
> attached as well.
>
> A pair of notes:
>
>   - The *_setcolor function stubs are being removed from some terminals
>   because grub_setcolor() from kernel already skips undefined *_setcolor
>   implementations so there's no need for an empty stub.  In fact, not
> needed for this patch but adds confusion (I had to inspect all them to see
> if *_getcolor() had to be added).
>
>   - I know that hardcoding colors is not so nice, but I was unsure how
> would the selection interface have to look like (and lacking time to
> implement it), and in comparison with defaulting to hardcoded 0x07 (grey on
> black) I see it as an improvement.

I still prefer to keep the default as it is. I like that a user (or a 
distributor) would modify the colors in grub.cfg.

Anyway, this will be a temporary hack, right? I'd love to see a fancier 
interface built in. Mmh, I really need to allocate time to implement one...

Okuji




  parent reply	other threads:[~2007-12-24 19:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-23 21:09 [PATCH] colored menu Robert Millan
2007-12-24  1:28 ` Robert Millan
2007-12-24  1:35   ` gfxterm / grub_virtual_screen_setcolorstate() Robert Millan
2007-12-29 23:50     ` Vesa Jääskeläinen
2008-01-23 12:23       ` Marco Gerards
2008-01-23 13:07         ` Robert Millan
2007-12-24 19:46 ` Yoshinori K. Okuji [this message]
2007-12-25  9:26   ` [PATCH] colored menu Robert Millan
2007-12-25 10:27     ` Yoshinori K. Okuji
2007-12-25 11:16       ` Robert Millan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200712242046.29638.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.