steveb@mako.UUCP (10/13/84)
I believe rogue is incorrect when it puts out the "vs" termcap entry upon startup as well as putting out "ti". "ti" is appropriate: it is the "string to begin programs that use cm" (cm is direct cursor addressing) but "vs" is the "sequence to start open/visual mode" also from the man page: "The ma, vs, and ve entries are specific to the vi program." Thus, there is no way rogue should be using vs. Rogue's use of vs means there is no way I can use the same termcap for vi and rogue if I want the vs string to do a bunch of vi-specific stuff, WHICH IS EXACTLY WHAT IT'S INTENDED FOR. Can anyone justify rogue's use of vs, or is it agreed that it is wrong?
robert@gitpyr.UUCP (Robert Viduya) (10/16/84)
> > I believe rogue is incorrect when it puts out the "vs" termcap entry upon > startup as well as putting out "ti". > I agree. I use the 'vs' and 've' controls to switch terminal screen pages. That way, I can use vi and still retain the contents of my screen from before i started vi. Unfortunately, while this trick also works with rogue, when I die, the screen draws the grave stone, spits out the 've' (which means, at 9600 baud, I miss seeing how much gold I'd accumulated), says 'Press enter to continue' (or something like that), and then gives me the score ratings. I've gotten used to it, but it's kind of hard to explain to a novice user. It also means that next time I crank up the editor, I see this big grave stone on my screen for a second before vi fills the screen in. robert -- Robert Viduya Office of Computing Services Georgia Institute of Technology, Atlanta GA 30332 Phone: (404) 894-4669 ...!{akgua,allegra,amd,hplabs,ihnp4,masscomp,ut-ngp}!gatech!gitpyr!robert ...!{rlgvax,sb1,uf-cgrl,unmvax,ut-sally}!gatech!gitpyr!robert
knutson@ut-ngp.UUCP (Jim Knutson) (10/16/84)
The termcap capabilities vs and ve are NOT vi/ex specific. It is used to set up a visual standout mode which vi/ex would like since it is screen oriented. The man page states that "these can be used to change, e.g., from a underline to a block cursor and back." This is not supposed to be a string that sets up the screen/micro/whatever for vi editing (don't use it to program your function keys for vi editing).
gwyn@brl-tgr.ARPA (Doug Gwyn <gwyn>) (10/16/84)
> I believe rogue is incorrect when it puts out the "vs" termcap entry upon > startup as well as putting out "ti". Sorry, but you are mistaken. You should have replaced your antique termcap manual page with the one I posted to net.sources some time ago. "vs" means "make cursor very visible", which is essential to Rogue. The only vi-specific terminal capability is "ma", which is an obsolete kludge for vi version 2 (non-overlaid version for 16-bit machines).
cpf@lasspvax.UUCP (Courtenay Footman) (10/17/84)
In article <335@mako.UUCP> steveb@mako.UUCP writes: > >I believe rogue is incorrect when it puts out the "vs" termcap entry upon >startup as well as putting out "ti". >.... >Can anyone justify rogue's use of vs, or is it agreed that it is wrong? It is quite simple. Rogue undoubtably uses curses to handle screen movement. Curses initializes the terminal in a routine setterm(), called by initscr(). Setterm has in it the lines _puts(TI); _puts(VS); . Thus *any* program that uses the default screen handling program (curses) will put out both the TI string and the VS string. This explains why rogue uses VS; it does not explain why curses does. (The person who wrote curses states that he used much code from vi; this probably slipped through; whether it is necessary I don't know.) See the document "Screen Updating and Cursor Movement Optimization: A Library Package", by K. Arnold in UPM 2C for more details. -- Courtenay Footman arpa: cpf@lnsvax Newman Lab. of Nuclear Studies usenet: cornell!lnsvax!cpf Cornell University