From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: multi-terminal in experimental
Date: Sat, 26 Dec 2009 17:39:09 +0100 [thread overview]
Message-ID: <4B363C2D.2030402@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 970 bytes --]
Hello, all. Today I merged multi-terminal by Robert (multi-input) and me
(multi-output) into experimental. One menu viewer instance is created
per output. This prompted for changing a bit a syntax for gfxmenu. Now
gfxmenu is attempted if 3 conditions are met:
-gfxmenu.mod is loaded. Do we need autoloading?
-output terminal is gfxterm
-theme variable is set.
menuviewer variable isn't used anymore
Another benefit is that now pressing 'e' in gfxmenu instead of doing
nothing (since graphical editor is unavailable) calls normal editor. In
future we may want to add few decorations (like how we render text with
instructions or the text to be edited) when editor is running together
with gfxmenu but it's not necessary.
Low-quality jpg screenshot with gfxmenu is attached (high-quality is
available on request)
Another screenshot is presented on Robert's blog.
Happy holidays to everyone.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #1.2: gfxmultiwinter_cropped.jpg --]
[-- Type: image/jpeg, Size: 71145 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next reply other threads:[~2009-12-26 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-26 16:39 Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-01-07 19:26 ` multi-terminal in experimental 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=4B363C2D.2030402@gmail.com \
--to=phcoder@gmail.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.