From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: pretty colors in gfxterm
Date: Sat, 5 May 2007 18:49:02 +0200 [thread overview]
Message-ID: <20070505164902.GA13762@aragorn> (raw)
In-Reply-To: <87bqgzns7g.fsf@xs4all.nl>
On Sat, May 05, 2007 at 06:36:03PM +0200, Marco Gerards wrote:
> Robert Millan <rmh@aybabtu.com> writes:
>
> Hi Robert,
>
> > Is it possible to archieve a similar effect to what "color cyan/blue white/blue"
> > does in grub legacy, but with grub2 gfxterm?
>
> You could implement a color command, which does the same as the color
> command in GRUB Legacy. All terminals have support for the color
> command. Although I am not really sure if it is completely compatible
> with what you are used to.
Can you give some pointer to that?
> Although, it would be better to implement what Okuji proposed a while
> ago. Are you willing to work on this? It might be fun to do so :-).
Willing yes, capable not. Lacking time and skill. Skill can still improve,
but time.... :-/
> If having a color command means that GRUB 2 will be used more, I am
> willing to add such command. Okuji, do you object?
Yes, I think so. But as said on IRC, I don't think the interface has to be
a color command. As long as we can display something that is not uglier
than "color cyan/blue white/blue" (and we don't have to wait ages untill the
new fancy menu is ready), that's ok.
> But I am only
> willing to add this if the Debian people ensure me that they will
> switch to whatever fancy graphics system we implement in the future,
> when it is ready ;-).
I'm all for that, at least in desktops.
--
Robert Millan
My spam trap is honeypot@aybabtu.com. Note: this address is only intended
for spam harvesters. Writing to it will get you added to my black list.
next prev parent reply other threads:[~2007-05-05 16:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 16:30 pretty colors in gfxterm Robert Millan
2007-05-05 16:36 ` Marco Gerards
2007-05-05 16:49 ` Robert Millan [this message]
2007-05-07 19:18 ` Yoshinori K. Okuji
2007-05-07 21:00 ` Robert Millan
2007-05-08 13:36 ` Robert Millan
2007-05-08 20:09 ` Yoshinori K. Okuji
2007-05-08 20:19 ` Otavio Salvador
2007-05-09 22:10 ` Yoshinori K. Okuji
2007-05-09 22:35 ` Otavio Salvador
2007-05-09 21:27 ` Robert Millan
2007-05-05 16:51 ` Otavio Salvador
2007-05-07 19:14 ` Yoshinori K. Okuji
[not found] <200705061558.l46Fw22b030347@correoredir01.dinaserver.com>
2007-05-07 14:39 ` adrian15
2007-05-07 18:45 ` Marco Gerards
2007-05-07 19:04 ` Robert Millan
2007-05-07 19:32 ` Yoshinori K. Okuji
2007-05-07 19:48 ` Yoshinori K. Okuji
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=20070505164902.GA13762@aragorn \
--to=rmh@aybabtu.com \
--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.