On Fri, 30 Aug 1996, Casper BodenCummins wrote:
> Have you tried stty rows 24?
Wow! That actually fixes lynx! It even took care of the pre and post line
trash that was being left behind before.
Joe, however is still exhibiting some very strange behavior. First, if I
try to scroll across a line wi
>Here's what I have in /ect/profile to do what I think you want;
>--cut-
>TTYTYPE=`tty|cut -f 3 -d /|grep -f - /etc/ttytype|cut -f 1 -d " "`
> if [ "$TTYTYPE" = "" ]; then
> :
> else
> TERM=$TTYTYPE
> fi
>
>unset TTYTYPE
>--
Dale,
> What I was looking for was more like what Gerry suggested.
> I also tried your suggestion on the LINES environment variable with little
> success.
> This is a REALLY DUMB terminal.
Have you tried stty rows 24?
> Is the syntax for this structure documented in the bash manual page? Can I
>
Miquel van Smoorenburg writes:
>
> In article <[EMAIL PROTECTED]>,
> Dale Scheetz <[EMAIL PROTECTED]> wrote:
> >I have a Data General "dumb" terminal hooked up to my linux box through a
> >hard wired serial port. The terminal seems to provide 24 lines on the
> >screen. Pine handles this fine, but
On Wed, 28 Aug 1996, Dale Scheetz wrote:
[...]
> This bring up another issue. This terminal obviously has special needs. Is
> there a way in /etc/profile (or somewhere else) to set up the proper
> conditions based on the terminal rather than the user? That is, can I
> determine at login time what
On Thu, 29 Aug 1996, Miquel van Smoorenburg wrote:
> Well yeah, if you run agetty (which is /sbin/getty on Debian ofcourse)
> you can put the terminal type at the end of the command line. For example
> if your terminal is a vt100, then in /etc/inittab:
>
> S1:23:respawn:/sbin/getty /dev/ttyS1 960
On Wed, 28 Aug 1996, Gerry Jensen wrote:
> I have this in my .bash_profile to set my terminal to vt320 if I'm
> calling in on the phone which I rarely do anymore::
>
> TTY=`tty`
> case $TTY in
> /dev/ttyS?) TERM=vt320 ;;
> esac
>
Thanks! This let me; 'stty cstopb' to fix login's insistance tha
You (Dale Scheetz) wrote:
> On 28 Aug 1996, Miquel van Smoorenburg wrote:
>
> > Probably a terminfo problem. Your terminal may have auto-wrap (auto-margins)
> > and terminfo says it doesn't, or vice verse. Also make sure that you do
> > have the right terminfo entry: if you set term to "linux" its
On Wed, 28 Aug 1996, Dale Scheetz wrote:
> On 28 Aug 1996, Miquel van Smoorenburg wrote:
>
> > Probably a terminfo problem. Your terminal may have auto-wrap (auto-margins)
> > and terminfo says it doesn't, or vice verse. Also make sure that you do
> > have the right terminfo entry: if you set ter
On 28 Aug 1996, Miquel van Smoorenburg wrote:
> Probably a terminfo problem. Your terminal may have auto-wrap (auto-margins)
> and terminfo says it doesn't, or vice verse. Also make sure that you do
> have the right terminfo entry: if you set term to "linux" its terminfo
> entry says it has 25 lin
On Wed, 28 Aug 1996, Dale Scheetz wrote:
> Is there an environment variable that I can set to 24
> (or even smaller) that will make joe and lynx handle the screen correctly?
The variable is LINES. resize(1x) will output code to set LINES and
ROWS correctly. I use it like this (this is a bash fu
In article <[EMAIL PROTECTED]>,
Dale Scheetz <[EMAIL PROTECTED]> wrote:
>I have a Data General "dumb" terminal hooked up to my linux box through a
>hard wired serial port. The terminal seems to provide 24 lines on the
>screen. Pine handles this fine, but joe and lynx behave as though there
>were o
I have a Data General "dumb" terminal hooked up to my linux box through a
hard wired serial port. The terminal seems to provide 24 lines on the
screen. Pine handles this fine, but joe and lynx behave as though there
were one more line than there actually is. The behavior is that as you
cursor down
13 matches
Mail list logo
