Bug report--window driver 3.51 bogosity during window switch

[Jim Rosenberg]

In article <4789 at cbmvax.UUCP> ditto at cbmvax.UUCP (Michael "Ford" Ditto) writes:
>speaking of stupid things
>that happen when you switch windows, there's another one that I can't
>stand.  Switching windows causes a SIGWIND signal to be sent, apparrently to
>the whole process group.  Usually, this is harmless, but certain programs
>seem to be confused by this.  For example, if you bang out to a shell from
>the "less" program (type "!sh"), and then switch windows, less will think
>the shell has exited and start reading the keyboard again. This results in a
>big mess.

Hmm.  I thought that unlike most signals, the default for SIGWIND if you don't
issue a signal() is SIG_IGN.  If less is failing to ignore the SIGWIND then
presumably it must be catching it.  I haven't poked into the code for less, but
this sounds like something that's fixable by hacking less.  Try taking a gander
at where it's catching signals.

There are a lot of things about the 3b1 interface that I'm not fond of, but
sending SIGWIND doesn't seem too bad to me if the default is SIG_IGN.  I have
a hunch that SIGWIND is used on other systems (Suns???) in ways that might not
be consistent with the 3b1, though.

Now what is inexcusable to me is this:  if they've got all the hooks for
SIGWIND why couldn't they have hacked vi so that it reinitialized curses on
SIGWIND and overrode the li and co entries so that they match the size of the
window???  Isn't this *JUST EXACTLY* what SIGWIND is supposed to be *FOR*??
-- 
 Jim Rosenberg
     CIS: 71515,124                         decvax!idis! \
     WELL: jer                                   allegra! ---- pitt!amanue!jr
     BIX: jrosenberg                  uunet!cmcl2!cadre! /