Subject: Fwd: screen trouble (some setdisplay stuff) and others...
To: None <port-arm32@NetBSD.ORG>
From: pwain@nc.com <PWAIN@nc.com>
List: port-arm32
Date: 01/06/1997 12:20:00
--=_ORCL_230092_0_11919701061325060
Content-Transfer-Encoding:7bit
Content-Type:text/plain; charset="US-ASCII"

> > There are 2 (count them :) fixes for this one. The first one is to just 
add  
> > the command 'tset' to your .cshrc/.profile file. This basically forces  
> > the shell that is runnning in the xterm to reread the termcap for the 
xterm.  
>  
> Ok, I'll check this, but in my .profile is a `tset' and I am even 
> using `xterm -ls' to open a new windoe. 
 
Hrm, well the '-ls' wont do too much (Why do you need it anyway :) Env 
variables 
are preserved into sub-shells so only things like aliases would apply and those 
should be in the .profile/.cshrc file). 
 
As for the tset, Im using the 'aliased' version that comes via the root .cshrc. 
Try changing the line to 'tset vt220' which wont affect the console (see 
previous 
mail) but will give the xterm a kick (xterms are pretty much vt220's anyway...) 
 
Another change you might want to consider is adding a 'bs' to the termcap for 
the xterm/vt220 terminals and rebuilding the termcap file. I cant remember what 
it was that was complaining about it (hack I think :), but that removed a lot 
of the terminal emulation problems too! 
 
Paul 
 
-- 
USA Liaison			Email: work: pwain@nc.com 
Acorn Network Computing		       home: wain@sirius.com 
Tel: +1 415 631 4628		 
Fax: +1 415 631 4683		URL:   http://www.brunel.ac.uk/~ccsrpsw/ 
 
Like Acorn would really have the same views as me! Get Real! :)

--=_ORCL_230092_0_11919701061325060
Content-Type:message/rfc822

Date: 06 Jan 97 10:19:46
From:"Jochen Scharrlach <jscharrl@BA-Stuttgart.De>" <jscharrl@BA-Stuttgart.De>
To:PWAIN
Subject:Re: screen trouble (some setdisplay stuff) and others...
Reply-to:jscharrl@BA-Stuttgart.De
MIME-Version: 1.0
Content-Transfer-Encoding:7bit
Content-Type:text/plain; charset="US-ASCII"

Hi,

> Well first off, look in /etc/monitor.conf to see which modes are avaliable 
> to X11. (This one is missing of course, which is why you cant see it). 

No, it isn't :) (if it was missing it would be impossible to tell
setvideo to choose this mode!)

> There are 2 (count them :) fixes for this one. The first one is to just add 
> the command 'tset' to your .cshrc/.profile file. This basically forces 
> the shell that is runnning in the xterm to reread the termcap for the xterm. 

Ok, I'll check this, but in my .profile is a `tset' and I am even
using `xterm -ls' to open a new windoe.

Thanks,
Jochen

-- 
                      ------------------------------------
                      EMail:   jscharrl@ba-stuttgart.de
                         or:   acorn1@ftp.uni-stuttgart.de
                      ------------------------------------

--=_ORCL_230092_0_11919701061325060--