Re: [PATCH] terminal split

[Robert Millan]

On Tue, Nov 04, 2008 at 04:52:20PM +0100, Yoshinori K. Okuji wrote:
> 
> No ChangeLog?

Here.  I ommitted it because I wanted to see if it would need big
adjustments first.

> 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.

Actually, I didn't think about this possibility.  My goal was to simplify
things on the backend side, so many of the quirks we have can be removed
(some examples in my previous mail), and we can integrate USB keyboard
support cleanly.

> This should 
> be trivial, once the input and output are separate, right?

Well, I suppose one could write a "pipe" output terminal that stores output
in a buffer, and then a "pipe" input terminal that reads from it.  My code
probably makes pipes easier, but I don't know how much is left (I assume you
don't want real pipes since that implies multi-threading).

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

terminal_split.diff
Description: Text Data