Re: Cygwin, ssh, and top
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 reason than it will cut down on some future traffic on this list. ;-) 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 sid and etch (unstable and testing, respectively). I'll get the package the file is in, and the differences in the termcap settings in a few. Need to make phone calls first - blasted job :P -- Spinning complacently in the darkness, covered and blinded by a blanket of little lives, false security has lulled the madness of this world into a slumber. Wake up! An eye is upon you, staring straight down and keenly through, seeing all that you are and everything that you will never be. Yes, an eye is upon you, an eye ready to blink. So face forward, with arms wide open and mind reeling. Your future has arrived... Are you ready to go? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin, ssh, and top
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 sid and etch (unstable and testing,
respectively).
I'll get the package the file is in, and the differences in the termcap
settings in a few. Need to make phone calls first - blasted job :P
And as an update:
# Reconstructed via infocmp from file: /lib/terminfo/c/cygwin
cygwin|ansi emulation for Cygwin,
am, hs, in, msgr, xon,
colors#8, it#8, pairs#64,
acsc=+\020\,\021-\030.^Y0\333`\004a\261f\370g\361h\260j\331k\277l\332m\300n\305o~p\304q\304r\304s_t\303u\264v\301w\302x\263y\363z\362{\343|\330}\234~\376,
bel=^G, bold=\E[1m, cbt=\E[Z, clear=\E[H\E[J, cr=^M,
cub=\E[%p1%dD, cub1=^H, cud=\E[%p1%dB, cud1=\E[B,
cuf=\E[%p1%dC, cuf1=\E[C, cup=\E[%i%p1%d;%p2%dH,
cuu=\E[%p1%dA, cuu1=\E[A, dch=\E[%p1%dP, dch1=\E[P,
dl=\E[%p1%dM, dl1=\E[M, ed=\E[J, el=\E[K, el1=\E[1K, fsl=^G,
home=\E[H, hpa=\E[%i%p1%dG, ht=^I, ich=\E[%p1%d@,
ich1=\E[@, il=\E[%p1%dL, il1=\E[L, ind=^J, invis=\E[8m,
kb2=\E[G, kbs=^H, kcub1=\E[D, kcud1=\E[B, kcuf1=\E[C,
kcuu1=\E[A, kdch1=\E[3~, kend=\E[4~, kf1=\E[[A,
kf10=\E[21~, kf11=\E[23~, kf12=\E[24~, kf13=\E[25~,
kf14=\E[26~, kf15=\E[28~, kf16=\E[29~, kf17=\E[31~,
kf18=\E[32~, kf19=\E[33~, kf2=\E[[B, kf20=\E[34~,
kf3=\E[[C, kf4=\E[[D, kf5=\E[[E, kf6=\E[17~, kf7=\E[18~,
kf8=\E[19~, kf9=\E[20~, khome=\E[1~, kich1=\E[2~,
knp=\E[6~, kpp=\E[5~, kspd=^Z, nel=^M^J, op=\E[39;49m,
rc=\E8, rev=\E[7m, ri=\EM, rmacs=\E[10m,
rmcup=\E[2J\E[?47l\E8, rmir=\E[4l, rmpch=\E[10m,
rmso=\E[27m, rmul=\E[24m, rs1=\Ec\E]R, sc=\E7,
setab=\E[4%p1%dm, setaf=\E[3%p1%dm,
sgr=\E[0;10%?%p1%t;7%;%?%p2%t;4%;%?%p3%t;7%;%?%p4%t;5%;%?%p6%t;1%;%?%p7%t;8%;%?%p9%t;11%;m,
sgr0=\E[0;10m, smacs=\E11m, smcup=\E7\E[?47h, smir=\E[4h,
smpch=\E[11m, smso=\E[7m, smul=\E[4m, tsl=\E];,
u6=\E[%i%d;%dR, u7=\E[6n, u8=\E[?6c, u9=\E[c,
vpa=\E[%i%p1%dd,
That's the output of infocmp cygwin on my laptop running debian sid.
As I've said, this works fine for me in both cmd and rxvt, including
with the 7x12 font David has said he prefers.
So it looks like the bug in question was caught and fixed already - I
suggest trying the package from testing first, then the one from
unstable if testing doesn't sort it..
The package in question is ncurses-base
Chris
--
Spinning complacently in the darkness, covered and blinded by a blanket
of little lives, false security has lulled the madness of this world
into a slumber. Wake up! An eye is upon you, staring straight down and
keenly through, seeing all that you are and everything that you will
never be. Yes, an eye is upon you, an eye ready to blink. So face
forward, with arms wide open and mind reeling. Your future has
arrived... Are you ready to go?
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
RE: Cygwin, ssh, and top
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/c/cygwin ... That's the output of infocmp cygwin on my laptop running debian sid. diff'ing that against Sarge: [EMAIL PROTECTED]:~/mydocuments/cygwin$ diff -w infocmp-cygwin-debian-3.1.out in focmp-cygwin-debian-sid.out 1c1 # Reconstructed via infocmp from file: /etc/terminfo/c/cygwin --- # Reconstructed via infocmp from file: /lib/terminfo/c/cygwin 4a5 5a7 24a27 25a29 29a34,36 Assuming empty lines have no effect, Sarge and Sid use the same terminfo settings. I wonder if top is different between Sarge and Sid? http://www.debian.org/distrib/packages#search_contents tells me that top is in package base/procps. My Sarge box has: [EMAIL PROTECTED]:~$ apt-cache showpkg procps | head -n 3 Package: procps Versions: 1:3.2.1-2(/var/lib/apt/lists/Debian%20GNU_Linux%203.1%20r0a%20%5fSar ge%5f%20-%20Official%20i386%20Binary-1%20(20050607)_dists_unstable_main_ binary-i386_Packages)(/var/lib/apt/lists/mirrors.kernel.org_debian_dists _stable_main_binary-i386_Packages)(/var/lib/apt/lists/ftp.us.debian.org_ debian_dists_stable_main_binary-i386_Packages)(/var/lib/apt/lists/linux. csua.berkeley.edu_debian_dists_stable_main_binary-i386_Packages)(/var/li b/dpkg/status) I use DOS line endings. Perhaps that's the cause of the bug? Run Cygwin setup, change line ending mode, test ssh and top -- problem still there. As I've said, this works fine for me in both cmd and rxvt, including with the 7x12 font David has said he prefers. So it looks like the bug in question was caught and fixed already - I suggest trying the package from testing first, then the one from unstable if testing doesn't sort it.. The package in question is ncurses-base I filed a bug report. Thomas Dickey seems to be hot on the trail: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=334289 Thanks! David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin, ssh, and top
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 $COLUMNS 80 Any other ideas? 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 COLUMNS (from 130 to 129 in my case), top worked correctly. I recommend running ssh from bash in an rxvt window instead of using the CMD.EXE window. This will give you an xterm terminal in Debian which will work much better. I use it all the time with Debian 3.1 and have no problems. -- David Rothenbergerspammer? - [EMAIL PROTECTED] GPG/PGP: 0x7F67E734, C233 365A 25EF 2C5F C8E1 43DF B44F BA26 7F67 E734 Kissing don't last, cookery do. -- George Meredith -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Cygwin, ssh, and top
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 COLUMNS (from 130 to 129 in my case), top worked correctly. I recommend running ssh from bash in an rxvt window instead of using the CMD.EXE window. This will give you an xterm terminal in Debian which will work much better. I use it all the time with Debian 3.1 and have no problems. 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 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. David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin, ssh, and top
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 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 out that rxvt can be used in place of CMD.EXE, which is what is started by the Cygwin icon created by setup. If you want to do that, here is my cygwin.bat: @echo off C: chdir C:\cygwin\bin rxvt -sl 1 -sr +sk -si -sw -fg Green -bg Black -e /bin/bash --login -i Obviously the path needs to be altered to whatever you have for your cygwin installation. I find this to be much more usable than using bash inside cmd.exe - things actually work. HTH, Chris -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin, ssh, and top
Chris Taylor wrote: David Christensen wrote: snip 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 out that rxvt can be used in place of CMD.EXE, which is what is started by the Cygwin icon created by setup. If you want to do that, here is my cygwin.bat: @echo off C: chdir C:\cygwin\bin rxvt -sl 1 -sr +sk -si -sw -fg Green -bg Black -e /bin/bash --login -i Obviously the path needs to be altered to whatever you have for your cygwin installation. I find this to be much more usable than using bash inside cmd.exe - things actually work. 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 reason than it will cut down on some future traffic on this list. ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin, ssh, and top
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? You might try vt102 as well. Also, consider using rxvt with Cygwin if you are using the stock CMD.EXE window. colors#8, cols#80, it#8, lines#25, ncv#3, pairs#64, I suspect it has something to do with the lines/columns settings. Try resizing the window before running top to make it recalculate size. Or run something like eval `resize`. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Cygwin, ssh, and top
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 correctly with Cygwin ssh and TERM=cygwin. Debian 3.1 is only slightly broken. My hosting provider uses an internally customized distribution based on Slackware; Cygwin ssh is just one of many issues. if you are using the stock CMD.EXE window. I use Cygwin Bash. I suspect it has something to do with the lines/columns settings. Try resizing the window before running top to make it recalculate size. Or run something like eval `resize`. Again, my preference is that the sshd host work correctly with the Cygwin ssh client. David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Cygwin, ssh, and top
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 make it recalculate size. Or run something like eval `resize`. Again, my preference is that the sshd host work correctly with the Cygwin ssh client. 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? -- René Berber -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Cygwin, ssh, and top
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 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
