Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!nrl-cmf!cmcl2!beta!unm-la!unmvax!charon!sdowdy
From: sdowdy@charon.unm.edu (Stephen Dowdy)
Newsgroups: comp.os.vms
Subject: Re: terminal width
Message-ID: <3033@charon.unm.edu>
Date: 6 May 88 19:06:17 GMT
References: <98*dahls@vax.elab.unit.uninett> <15403@uflorida.cis.ufl.EDU>
Reply-To: sdowdy@charon.unm.edu.UUCP (Stephen Dowdy)
Organization: University of New Mexico, Albuquerque, NM
Lines: 24

In article <15403@uflorida.cis.ufl.EDU> jdc@beach.cis.ufl.edu (Jeff Capehart) writes:
>If I remember correctly, the terminal width is only available through
>the status buffer (just like baud rate) when chatting with a device
>such as a terminal, using the $QIO function.  I have a little program
>which returns the baud rate of a terminal into a global symbol, and
>I am sure if could be adapted to return the terminal width also.
>--
>Jeff Capehart 		Internet: jdc@beach.cis.ufl.edu
>University of Florida	UUCP:   ..!ihnp4!codas!uflorida!beach.cis.ufl.edu!jdc	

This may be a fluke, but i once wrote a DCL Screen package, and needed to
know wether the term was in 80 or 132 column mode.  Turned out that a
F$GetDVI("TT:","DEVBUFSIZ") returned the terminal width.

--stephen dowdy
P.S. "Screen Package in *DCL*!  Yuck!".  It's the challenge.  Now, to
write a screen editor...
-- 
$!#######################################################################
$! stephen dowdy (UNM CIRT) Albuquerque, New Mexico, 87131 (505) 277-8044
$! Usenet:   {convex,ucbvax,gatech,csu-cs,anl-mcs}!unmvax!charon!sdowdy
$! BITNET:   sdowdy@unmb
$! Internet: sdowdy@ariel.unm.edu
$!      Team SPAM in '88!            SPAAAAAAAAAAAAAAAAAAAAMMMMMMM!
$!#######################################################################