Hi, a few weeks ago I reported a problem with rlogin not transmitting
the correct window size when run from cygwin. The fact that there was
no problem with telnet gnawed at me, so I investigated the code
differences and found that rlogin.c from the gnu inetutils distribution
(e.g. 1.4.2) has flawe
>$TERM is fine, but I found that forcing an eval `resize` on the remote
>side gets things to work. I'm still confused about why this is neccessary
>for cygwin (I tried the latest snapshot as Brian suggested to no avail).
>Also the difference between telnet and rlogin behavior seems unexpected
>to
> > Ah, things work with telnet but not rlogin ... does that hint at the
> > cause of the problem?
> I suspect there's some difference in the environment that is either
> propagated from the local machine or set via the shell startup files. Try
> checking the value of $TERM in both cases.
$TERM
On Wed, 4 Feb 2004, Harold Levy wrote:
> > > If I open a 32-row xterm and rlogin into a unix machine, then run vim or
> > > mutt or less, these apps think the bottom of the screen is at row 24 ...
> > > they don't use the rows beyond that.
> >
> > Right, now I understand. Do you have the $TERM se
> > If I open a 32-row xterm and rlogin into a unix machine, then run vim or
> > mutt or less, these apps think the bottom of the screen is at row 24 ...
> > they don't use the rows beyond that.
>
> Right, now I understand. Do you have the $TERM set correctly on the
> remote machine? Did you try
On Wed, 4 Feb 2004 Harold at Levy dot synopsys dot com wrote:
> Hi, when my cygwin terminals are sized to something other than 24 rows
> they don't work correctly with apps like vim/mutt/less when I connect to
> a remote unix system; these apps behave like they think the terminal
> has 24 rows. I
rlogin, to my knowledge, has nothing to do with the X protocol of
resizing.
After you resize your window, set some variables accordingly:
LINES=height
COLUMNS=width
export LINES COLUMNS
If you start with an xterm, you shouldn't have a problem, but since you
started with a console window and ju
On Wed, 4 Feb 2004, Harold Levy wrote:
> Thanks for the response Igor!
>
> >> Hi, when my cygwin terminals are sized to something other than 24 rows
> > I'm assuming you're talking about the command windows running bash.
>
> It happens whether running a command window with bash or running an xterm
Thanks for the response Igor!
>> Hi, when my cygwin terminals are sized to something other than 24 rows
> I'm assuming you're talking about the command windows running bash.
It happens whether running a command window with bash or running an xterm;
the fact that it happens in and out of xfree mad
On Wed, 4 Feb 2004 HaroldLevysynopsyscom wrote:
> Hi, when my cygwin terminals are sized to something other than 24 rows
I'm assuming you're talking about the command windows running bash.
> they don't work correctly with apps like vim/mutt/less when I connect to
> a remote unix system; these ap
Hi, when my cygwin terminals are sized to something other than 24 rows
they don't work correctly with apps like vim/mutt/less when I connect to
a remote unix system; these apps behave like they think the terminal
has 24 rows. It doesn't matter whether I use the bash shell or an
xterm, whether I se
11 matches
Mail list logo
