From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] terminal split
Date: Tue, 4 Nov 2008 16:52:20 +0100 [thread overview]
Message-ID: <200811041652.21150.okuji@enbug.org> (raw)
In-Reply-To: <20081102181132.GA24737@thorin>
On Sunday 02 November 2008 19:11:32 Robert Millan wrote:
> Hi,
>
> This patch splits terminal handling in input and output. While at it, it
> resolves/removes some of the kludges we had to work around this limitation.
>
> For example, gfxterm/vga no longer need to assume the input is bios
> console, at_keyboard can be used in combination with any output terminal,
> etc.
>
> It will also be possible to turn vga_text.c into a standalone output term,
> but this needs more work since it is currently sharing much code with the
> bios console in console.c.
No ChangeLog?
The idea is good. I agree with your patch, basically. I can review it more
seriously, once you write up ChangeLog entries.
BTW, I would like to obtain the capability of handling pipes, so that we can,
say, "help | more". I guess you have the same idea in your mind. This should
be trivial, once the input and output are separate, right?
Regards,
Okuji
next prev parent reply other threads:[~2008-11-04 15:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 18:11 [PATCH] terminal split Robert Millan
2008-11-04 15:52 ` Yoshinori K. Okuji [this message]
2008-11-04 17:14 ` Robert Millan
2008-11-06 17:05 ` Yoshinori K. Okuji
2008-11-07 19:13 ` Robert Millan
2008-11-04 18:31 ` Vesa Jääskeläinen
2008-11-06 17:20 ` Yoshinori K. Okuji
2008-11-07 19:07 ` Robert Millan
2008-11-09 7:22 ` Yoshinori K. Okuji
2008-11-04 18:53 ` Vesa Jääskeläinen
2008-11-04 19:12 ` Robert Millan
2008-11-04 19:49 ` Colin D Bennett
2008-11-07 19:26 ` [RFC] Multi-terminal support (Re: [PATCH] terminal split) Robert Millan
2008-11-22 17:42 ` Yoshinori K. Okuji
2008-11-22 19:54 ` Robert Millan
2008-11-25 21:23 ` Yoshinori K. Okuji
2008-11-26 11:41 ` SPAM-LOW: " Amin Azez
2008-11-28 20:38 ` Robert Millan
2008-11-29 21:20 ` Vesa Jääskeläinen
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=200811041652.21150.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.