Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!clyde!cuae2!gatech!babar!gtss!chas
From: chas@gtss.UUCP (Charles Cleveland)
Newsgroups: comp.sys.amiga
Subject: Re: Problem with VT100 v2.3
Message-ID: <159@gtss.UUCP>
Date: Thu, 4-Dec-86 15:00:51 EST
Article-I.D.: gtss.159
Posted: Thu Dec  4 15:00:51 1986
Date-Received: Fri, 5-Dec-86 06:36:06 EST
References: <67@linus.UUCP> <448@hao.UUCP>
Reply-To: chas@gtss.UUCP (Charles Cleveland)
Organization: Georgia Tech Surface Studies
Lines: 65


In article <448@hao.UUCP> hull@hao.UUCP (Howard Hull) writes:
>
>I suspect that there are two problems, one easy and the other yet unidentified.
>If you set VOLUME to 64 in vt100.h and compile under Manx, then setting
>VOLUME to 0 in vt100.init produces neither sound nor flash.  But if you set
>VOLUME to 0 in vt100.h under Manx, then set VOLUME to 64 in vt100.init,
>you get sound, or if you set VOLUME to 0 in vt100.init, you get the flash
>like you're supposed to.  That's the easy one.
>
I got a Lattice 3.03 compilation of 2.3 to flash when setting volume to zero
in vt100.init when vt100.h had a finite volume by changing in init.c the line
	if(i > 0) p_volume = i;
which apparently makes it impossible to set the volume to zero if it is not
so set in vt100.h, to
        if(i >= 0) p_volume = i;
I truly don't under stand how, with MANX, setting volume to zero in a .init
file can have any effect on the program's behavior as compared with not
setting it at all.  So I probably missed something.

In any case, I'm still beepless.

I also added support for cursor application keys in addition to keypad
application keys.  Wecker assumes that if keypad application keys are
on that cursor application keys are too (another poster suggested that
the cursor application keys be left off at all times).  Depends on the
host (and what program it's running).  Wecker's method works fine on
my UNIX hosts but not on Cybers, which I also use from time to time.
Since most readers of this column use UNIX, and they *all* could easily
manage this change for themselves, I have refrained from posting the
diffs.  However, if interest demonstrates itself I will do so.

However, I have another problem which I have still not tracked down.
If I use an .init file (mine are never called vt100.init, of course)
my version of vt100 forgets what the keyscript character is and also
forgets what F1 is supposed to do.  I have so far just added these
to my .init files, a crude but effective solution which leaves me
vaguely uneasy.  This was something I hoped would go away with 2.3.
Has anybody else out there seen anything like this?  It predates my
modifications.

Oh yeah, there's one thing that Lattice barfs on.  In kermit.c in
the routine multi_xfer() there is a 'return();'.  Since return is not
a function and () is a pretty peculiar expression, K&R (and Lattice) have
every right to be upset.  I deleted the () and changed the declaration of
multi_xfer to void, since it never returns a value.

Regards.

-- 
Charles Cleveland			chas@ss.physics.gatech.edu
Georgia Tech School of Physics
Atlanta, GA 30332			Georgia Tech Surface Studies

...!{akgua,allegra,amd,hplabs,ihnp4,masscomp,ut-ngp,rlgvax,sb1,
	uf-cgrl,unmvax,ut-sally}!gatech!gtss!chas


-- 
Charles Cleveland			chas@ss.physics.gatech.edu
Georgia Tech School of Physics
Atlanta, GA 30332			Georgia Tech Surface Studies

...!{akgua,allegra,amd,hplabs,ihnp4,masscomp,ut-ngp,rlgvax,sb1,
	uf-cgrl,unmvax,ut-sally}!gatech!gtss!chas