Chris Taylor wrote:
> he also seems to be under the impression that cygwin bash is only
> cygwin bash when you start it from an unaltered cygwin.bat - ie
> using cmd.exe, which is most assuredly not the case.
Yup. I plead ignorance.
> # Reconstructed via infocmp from file: /lib/terminfo/
Chris Taylor wrote:
True, but he also seems to be under the impression that cygwin bash is
only cygwin bash when you start it from an unaltered cygwin.bat - ie
using cmd.exe, which is most assuredly not the case.
In the meantime.. *tests with debian sid and etch*
Works perfectly with both si
Larry Hall (Cygwin) wrote:
I think what David is saying here is that if there weren't a bug in Debian
3.1 terminal settings, this would work either way, just as it did in 3.0.
Regardless of the workarounds for the bug, there is still a bug and it's
worthwhile getting it fixed, if for no other re
Chris Taylor wrote:
David Christensen wrote:
My preference is still that Cygwin bash ssh work correctly with Debian
3.1, and
I believe the problem is with whatever package provides terminal stuff
in Debian
3.1. I'll try to find the package and file a bug report.
It should be pointed ou
David Christensen wrote:
Invoking rxvt from a Cygwin Bash shell and then ssh'ing into Debian and
customized Slackware gives me the same results as Putty -- e.g. everything works
on Debian 3.0 and 3.1, and the customized Slackware is messed up.
My preference is still that Cygwin bash ssh work co
David Rothenberger wrote on cygwin:
> Try setting COLUMNS to 79 with the comment "export COLUMNS=79".
> I had this problem when I ran the Cygwin ssh client from bash *in a
> CMD.EXE window*. For some reason, Debian miscalculated the COLUMNS
> size; it was 1 column too large. When I manually set CO
On 10/15/2005 8:43 PM, David Christensen wrote:
René Berber wrote:
Yes but... the problem is caused by the terminfo data you showed:
columns is not defined.
Try "echo $COLUMNS"... now "export COLUMNS=80; top"; does it work?
COLUMNS is getting set someplace:
[EMAIL PROTECTED]:~$ echo $CO
René Berber wrote:
> Yes but... the problem is caused by the terminfo data you showed:
> columns is not defined.
> Try "echo $COLUMNS"... now "export COLUMNS=80; top"; does it work?
COLUMNS is getting set someplace:
[EMAIL PROTECTED]:~$ echo $COLUMNS
80
Any other ideas?
David
--
Uns
David Christensen wrote:
[snip]
>>if you are using the stock CMD.EXE window.
>
> I use Cygwin Bash.
Using rxvt has the advantage that one of its parameters enables changing TERM.
>>I suspect it has something to do with the lines/columns settings.
>>Try resizing the window before running top to m
Brian Dessent wrote on cygwin:
> You're setting TERM before connecting?
Yes.
> Have you verified that the setting is indeed changed once you are
> logged on to the remote?
Yes.
> You might try "vt102" as well. Also, consider using rxvt with Cygwin
I prefer that the machines I log into work c
David Christensen wrote:
> 3. Setting Cygwin TERM to xterm and logging in to either Debian machine has
> no
> effect on top, and now the cursor keys are broken.
You're setting TERM before connecting? Have you verified that the
setting is indeed changed once you are logged on to the remote? Yo
11 matches
Mail list logo
