Eighth Edition and job control (was Re: UNIX Futures)

Tim Smith tim at ism780c.UUCP
Tue Apr 22 13:18:30 AEST 1986


In article <1106 at psivax.UUCP> friesen at psivax.UUCP (Stanley Friesen) writes:
>
>	Actually, under UNIX the way to do this is have the windowing
>system send some standard signal, say SIGWINCH, to the process whose
>window is being changed. The default action for this signal would of
>course be to *ignore* it. If a process wants/needs to know about
>window changes it can arrange to catch the signal! This is consistant
>with the rest of the UNIX OS and is operationally equivalent to what
>you are talking about, since a program that doesn't need to know can
>simply do nothing at all.

I don't think that this is equivalent to what I want.  I want there to
be two types of procs: those that know about windows, and those that
don't.  Those that do would be told about window changes, probably
with a signal.  Those that don't would not know that they are on
a windowing system.  Their window would look like a terminal.  When
the user does something like change the size of the window, that would
not change the logical size of the window, just the physical size.

[ by the way, I am assuming a windowing system that keeps track of what
  is obscured by other windows, not one that requires procs to redraw
  their own screens.  Thus, the only window changes that a proc should
  care about are size changes ( and deletions... ) ]

Note that under this scheme I should be able to take vi or rogue, and
run them with no changes at all.
-- 
Tim Smith       sdcrdcf!ism780c!tim || ima!ism780!tim || ihnp4!cithep!tim



More information about the Comp.unix.wizards mailing list