Re: Looking for some help.

[Ed Greenberg <edg@greenberg.org>]

At 10:07 PM 1/15/98 -0600, John Schucker wrote:
>Well, the problem with dumping all the output to the port as I see it is 
>lack of review.  I mean, let's say you're doing cat foo.bar, and you miss 
>say a phone number.  How do you go back and look at just the line with 
>that number on it?  If you're simply dumping the output to the port, the 
>only way to do it is recat the file.
>  
>Mind, I'm not saying it's a bad idea or anything ... the more options the 
>better as far as I'm concerned .. and I could see it as especially useful 
>in a special pre-compiled kernel with that driver, so you could hook up a 
>synth and install linux yourself essentially.

I think the review problem is easy, actually. I plan to work on building a
review module into this code as soon as I have the flow control working
better.

I already have a rudamentary review going, in that when you switch from one
Virtual Console to another, the code rereads the screen as it repaints. This 
is done by actually looking at the (software) screen buffer.

Review could be by cursoring around the screen and asking for lines, words
or characters. I can already read the screen, as indicated above, so the
extent of 
the problem is making the keyboard a modal device, and then building the
review mode. 

I see all of this as taking place in keyboard.c and console.c.

The version that I have now starts talking as soon as you boot, and keeps
talking right down to "system halted." If flow control worked, I'd ask for
testers. 

</edg> 
--
Ed Greenberg               edg@greenberg.org            km6cg
                        http://www.greenberg.org/

---
Send your message for blinux-list to blinux-list@redhat.com
Blinux software archive at ftp://leb.net/pub/blinux
Blinux web page at http://leb.net/blinux
To unsubscribe send mail to blinux-list-request@redhat.com
with subject line: unsubscribe