Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!agate!bionet!apple!voder!pyramid!prls!mips!sultra!dtynan
From: dtynan@sultra.UUCP (Der Tynan)
Newsgroups: comp.os.minix
Subject: Re: 1.3c more notes
Summary: My opinion...
Message-ID: <2571@sultra.UUCP>
Date: 11 Oct 88 05:37:49 GMT
References: <3193@sdsu.UUCP> <1499@ast.cs.vu.nl>
Organization: Tynan Computers, Sunnyvale, CA
Lines: 31

In article <1499@ast.cs.vu.nl>, ast@cs.vu.nl (Andy Tanenbaum) writes:
> 
> In return for his doing this, I am willing to tolerate linewrapping (as an
> #ifdef), very much against my taste and better judgment.
> 
> If anyone has other suggestions for simplifying the video business, please
> post them so we can have a discussion.  These changes will apply to 1.4, not
> 1.3.  
> 
> Andy Tanenbaum (ast@cs.vu.nl)

Sorry to disagree with you, but personally, I favor line-wrap.  Unfortunately,
this is *not* a perfect world, and there are many programs which disappear
off the side of the screen.  I think it is the responsibility of the tty
driver to cure this.  For example, if you use term, and call a remote system,
which answers at a different speed, it takes a few lines of garbage before
you get any real data.  Unfortunately, at this stage, everything has
disappeared out of view.  I can cite numerous examples of programs that
behave this way, and unfortunately, it would take a lot to fix them all.

On the other point, I think the console driver should be split.  There should
be one for EGA, and one for the rest of us.  I know this is difficult to do,
because the distribution disks must work with both, so maybe a hybrid is in
order.  In other words, a quick-and-dirty tty driver, which works with both
types.  Once the system is running, the end-user can select the appropriate
code, and re-compile the kernel.  Somewhat similar to the xx_wini.c deal.
						- Der
-- 
Reply:	dtynan@sultra.UUCP		(Der Tynan @ Tynan Computers)
	{mips,pyramid}!sultra!dtynan
	Cast a cold eye on life, on death.  Horseman, pass by...    [WBY]