[comp.sys.amiga.datacomm] VLT and VI - DOn't Work very Well

yorkw@stable.ecn.purdue.edu (Willis F York) (02/11/91)

WGLP09@SLACVM.SLAC.STANFORD.EDU writes:

>talking to VLT's author? 8)
>       My policy: you send me a capture file of something that doesn't
>work or doesn't work correctly, and I will see what can be done within
>the limits of VLT's intended purpose (being a communication program
>for connecting to the IBM mainframe and to VAX/VMS). Quite frankly,
>if it works for me and the people here at SLAC, I have little incentive
>to emulate every little bug that's in the VT100 ROMs... But most of the
>time emulation problems are easy to fix and they usually make it into
>the next version.

I've noticed this problem with "scrolling" in VI, the last 4 lines scrolled
at  the bottom of the screen will get "Munged" but i think it was a problem with
using MoreRowa and having 33 (or so) lines...

(At least i haven't noticed it with the Newset version of VLT)

ps: In the menus with Subitems i think a the >> symbol looks Ugly..
I think a ... (3 dots) would look nicer..  :^)


ANyone Noticed Problems with VI and VLT? 

(How about explaining in ENGLISH what i do to get blink.scp to 
withstand the <esc> key)

 

--
yorkw@ecn.purdue.edu  
Willis F York   
(Hope THIS sig don't insult anyone!)

dfrancis@tronsbox.xei.com (Dennis Heffernan) (02/11/91)

	For the past few weeks, I've used nothing but VLT for my terminal (ever
since a buddy wrote a rexx-based autodialer for it; before that, I would 
boot up JRComm if I had to attack dial).  For the past year or so, I've used
nothing but VI as an editor on the Unix systems I call.  VLT, in ANY version,
has never failed me in handling VI.  The same is not true of JRComm.


dfrancis@tronsbox.xei.com   ...uunet!tronsbox!dfrancis     GEnie: D.HEFFERNAN1
"...when Fortran was introduced, it was claimed that Fortran would largely
eliminate coding and debugging!  Of course, that claim proved to be quite false"
- UNIVERSAL ASSEMBLY LANGUAGE, Robert M. Fitz & Larry Crocket 

mwm@pa.dec.com (Mike (My Watch Has Windows) Meyer) (02/12/91)

In article <yorkw.666235250@stable.ecn.purdue.edu> yorkw@stable.ecn.purdue.edu (Willis F York) writes:

   I've noticed this problem with "scrolling" in VI, the last 4 lines scrolled
   at  the bottom of the screen will get "Munged" but i think it was a problem
   with using MoreRowa and having 33 (or so) lines...

Could be a problem with your termcap. As others have notices, VLT
isn't a perfect VT100 emulation, so minor gotchas can make things go
wierd. Of course, minor changes in VLT might fix some of these, too.

   ps: In the menus with Subitems i think a the >> symbol looks Ugly..
   I think a ... (3 dots) would look nicer..  :^)

Yeah, I agree - it's ugly. But it's "the standard." "..." is reserverd
for meaning you're going to open a requester.

   (How about explaining in ENGLISH what i do to get blink.scp to 
   withstand the <esc> key)

Um, change the name of the label to something that starts (or is it
ends) with a '$' (dollar sign). Look in the update notes for 5.034.

	<mike
--
Es brillig war. Die schlichte Toven			Mike Meyer
Wirrten und wimmelten in Waben;				mwm@pa.dec.com
Und aller-mumsige Burggoven				decwrl!mwm
Die mohmem Rath' ausgraben.

WGLP09@SLACVM.SLAC.STANFORD.EDU (02/12/91)

       As to the >> marks in the menu to indicate submenus, sorry, but that's
in the new 2.0 "Style Guide" and is "blessed by a higher authority". 8)
       If you have any problems with vi that can't be fixed by changing
some of the "Operation" settings, send me a capture file of a session
where it goes wrong, with a not explaining what you're doing. I don't
have access to a UNIX system (and I don't want to either and if I did
you wouldn't catch me dead using vi...) so that's why I ask for a capture
file.
       To make your blinker impervious to the escape key make it like this:

      $blinker: cursorh 0; delay .3; cursorh 2; delay .3; goto $blinker

The trick is the $ sign that starts the label. Such scripts can only be
stopped by cancelling them explicitly by name. Now that the script is
impervious to the escape key, the escape key will do its normal job, namely
send an escape.

       Willy.
----------
Willy langeveld - Bitnet: WGLP09 @ SLACVM - BIX: langeveld

yorkw@stable.ecn.purdue.edu (Willis F York) (02/12/91)

WGLP09@SLACVM.SLAC.STANFORD.EDU writes:
>      $blinker: cursorh 0; delay .3; cursorh 2; delay .3; goto $blinker
Ok Thanx.. The above line  goes into a blinky.scp file (Right?)
then i Run the script from VLT.. (Right?)

PS: 

WHY???? Have the ESC key Kill the Scripts? 
Why not a "programable" key.. (Or better yet A-K for Kill..)

Ya get an A for VLT.. Ya'd get an A+ if it CAME with the Manual
in latex format..

I was going to complain about VLT wanting the "special" fonts when
i "NEVER" use them.. But why bother...

ps: If i rezide the window, and VLT "Dissiaperes" because it can't find a 
Font, it shoulden't DIE..... Have it BEEP and go back to "normal"
(Perhaps ya fixed this in the newerone..)



>----------
>Willy langeveld - Bitnet: WGLP09 @ SLACVM - BIX: langeveld


--
yorkw@ecn.purdue.edu  
Willis F York   
(Hope THIS sig don't insult anyone!)

WGLP09@SLACVM.SLAC.STANFORD.EDU (02/13/91)

      I don't think VLT 5.034 dies anymore when you didn't install the fonts,
unless it can't find topaz 8 either. But then you're up the creek anyhow...

      Willy.
----------
Willy langeveld - Bitnet: WGLP09 @ SLACVM - BIX: langeveld