problems with top using Cygwin ssh to Debian 31r0a

problems with top using Cygwin ssh to Debian 31r0a

[David Christensen]

Cygwin:

When I use Cygwin to ssh into a Debian 3.1 stable ("Sarge") machine and run
"top", the newlines seem to be double-expanded -- e.g. there is a blank line
between each line of information.  This problem does not occur when I ssh into a
Debian 3.0 stable ("Woody") machine.  This problem does not occur on either
Debian machine if I use Putty.


Any suggestions?


TIA,

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: problems with top using Cygwin ssh to Debian 31r0a

[Larry Hall (Cygwin)]

David Christensen wrote:
> Cygwin:
> 
> When I use Cygwin to ssh into a Debian 3.1 stable ("Sarge") machine and run
> "top", the newlines seem to be double-expanded -- e.g. there is a blank line
> between each line of information.  This problem does not occur when I ssh into a
> Debian 3.0 stable ("Woody") machine.  This problem does not occur on either
> Debian machine if I use Putty.
> 
> 
> Any suggestions?


Perhaps you've implied something you didn't intend but if using Cygwin's
ssh works with Debian 3.0 but not with Debian 3.1, I'd suspect something
on the Debian side.  Sounds like a terminal problem to me.  Do both
understand your terminal setting?

-- 
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: problems with top using Cygwin ssh to Debian 31r0a

[David Christensen]

Larry Hall wrote:
> Perhaps you've implied something you didn't intend

I try to run all my machines and applications -- Windows, Cygwin, Debian, etc.
-- with "official" packages and "out of the box" configurations as much as
possible.  I don't believe I've messed with anything related to terminals
(terminfo ?) on either Debian machine; I wouldn't even know where to start.


> but if using Cygwin's ssh works with Debian 3.0 but not with Debian
> 3.1, I'd suspect something on the Debian side.  Sounds like a
> terminal problem to me.

That's what I thought, so I posted a question to the debian-user list and the
suggestion came back that I test with something other than Cygwin ssh.  So, I
tested with Putty and Putty works fine with both Debian 3.0 and 3.1.  So, now
I'm posting the question here.


> Do both understand your terminal setting?

I don't see any complaints when I log into a Debian machine.


How can I troubleshoot this?


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: problems with top using Cygwin ssh to Debian 31r0a

[René Berber]

David Christensen wrote:
[snip]
>>Do both understand your terminal setting?
> 
> I don't see any complaints when I log into a Debian machine.
> 
> How can I troubleshoot this?

Use "echo $TERM" on both machines and see if there is any difference.

Next, if there is no difference, try setting TERM to xterm on the remote side
and see if the problem persist.
-- 
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: problems with top using Cygwin ssh to Debian 31r0a

[Larry Hall (Cygwin)]

On 10/15/2005, David Christensen wrote:
> >Do both understand your terminal setting?
> 
> 
> I don't see any complaints when I log into a Debian machine.
> 
> 
> How can I troubleshoot this?
> 

Check what your terminal type is ('echo $TERM').  It's probably 'cygwin' for
Cygwin if you're running from a command prompt.  You can use 'infocmp' to
compare the 'cygwin' terminal definitions (under '/usr/share/terminfo/c') on
your Debian machines to see if there's something different between the two.
You can also check the terminal used by Putty.  I'm sure that's not going
to be 'cygwin'.  Try setting TERM to that before you 'ssh' into your
problem Debian system and see if that helps.  If so, that system has a
missing or wrong entry in it's terminfo DB.  The solution in that case is to
copy the entry from the working system to the non-working one.  Alternatively,
you can choose to side-step the issue by setting a different terminal, as I
mentioned above.

-- 
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/

Cygwin, ssh, and top

[David Christensen]

debian-user:

I've been chasing a problem with Cygwin ssh and Debian 3.1 top.  Here's my
original posting to debian-user:

-----Original Message-----
From: David Christensen [mailto:dpchrist@holgerdanske.com] 
Sent: Friday, June 10, 2005 9:13 PM
To: 'debian-user@lists.debian.org'
Subject: Cygwin, ssh, and top

debian users:

When I ssh into one of my Debian 3.0 boxes from WinXP Pro/ Cygwin, top works as
expected.

When I ssh into my Debian 3.1 box from WinXP Pro/Cygwin, top seems to be
inserting multiple line feeds at the end of each line:

   4 root       5 -10     0    0    0 S  0.0  0.0   0:00.01 khelper

  20 root       5 -10     0    0    0 S  0.0  0.0   0:00.00 kblockd/0

  44 root      15   0     0    0    0 S  0.0  0.0   0:01.44 pdflush

  46 root       5 -10     0    0    0 S  0.0  0.0   0:00.00 aio/0

  45 root      15   0     0    0    0 S  0.0  0.0   0:00.75 kswapd0

 182 root      25   0     0    0    0 S  0.0  0.0   0:00.00 kseriod

 202 root       6 -10     0    0    0 S  0.0  0.0   0:00.00 ata/0

1040 root      15   0     0    0    0 S  0.0  0.0   0:00.00 khubd

1840 root      15   0  2376  864 2164 S  0.0  0.3   0:00.00 dhclient

1846 daemon    16   0  1612  460 1440 S  0.0  0.2   0:00.00 portmap

2181 root      16   0  2260  820 2092 S  0.0  0.3   0:00.02 syslogd

Any ideas?

TIA,

David


The replies I received and the troubleshooting I did made me think that the
problem was with Cygwin.  So, I posted to the Cygwin list:

-----Original Message-----
From: David Christensen [mailto:dpchrist@holgerdanske.com] 
Sent: Friday, October 14, 2005 5:46 PM
To: cygwin@cygwin.com
Subject: problems with top using Cygwin ssh to Debian 31r0a

Cygwin:

When I use Cygwin to ssh into a Debian 3.1 stable ("Sarge") machine and run
"top", the newlines seem to be double-expanded -- e.g. there is a blank line
between each line of information.  This problem does not occur when I ssh into a
Debian 3.0 stable ("Woody") machine.  This problem does not occur on either
Debian machine if I use Putty.

Any suggestions?

TIA,

David


The replies I received and troubleshooting I've done now tell me it's really a
Debian 3.1 problem.

Here are my latest efforts:

1.  Cygwin ssh TERM is cygwin on both Debian machines.

2.  Putty TERM is xterm.

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.

4.  Here is infocmp output on Debian 3.0:

dpchrist@p166d302:~$ infocmp cygwin
#       Reconstructed via infocmp from file: /usr/share/terminfo/c/cygwin
cygwin|ansi emulation for Cygwin,
        am, eo, in, msgr, xon,
        colors#8, cols#80, it#8, lines#25, ncv#3, 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, clear=\E[H\E[J, cr=^M, cub1=^H,
        cud1=\E[B, cuf1=\E[C, cup=\E[%i%p1%d;%p2%dH, 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, home=\E[H, hpa=\E[%i%p1%dG, ht=^I,
        hts=\EH, ich=\E[%p1%d@, ich1=\E[@, il=\E[%p1%dL, il1=\E[L,
        ind=^J, invis=\E[8m, 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, 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, smir=\E[4h, smpch=\E[11m, smso=\E[7m,
        smul=\E[4m, u6=\E[%i%d;%dR, u7=\E[6n, u9=\E[c,
        vpa=\E[%i%p1%dd,
dpchrist@p166d302:~$

5. Here is infocmp output on Debian 3.1:

dpchrist@p166v:~$ infocmp cygwin
#       Reconstructed via infocmp from file: /etc/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,

6. Here is the difference:

<CVSENV>dpchrist@p42800e:~/mydocuments/cygwin$ diff -d debian-30-infocmp.out de
bian-31-infocmp.out
1c1
< #     Reconstructed via infocmp from file: /usr/share/terminfo/c/cygwin
---
> #     Reconstructed via infocmp from file: /etc/terminfo/c/cygwin
3,4c3,4
<       am, eo, in, msgr, xon,
<       colors#8, cols#80, it#8, lines#25, ncv#3, pairs#64,
---
>       am, hs, in, msgr, xon,
>       colors#8, it#8, pairs#64,
6,12c6,14
<       bel=^G, bold=\E[1m, clear=\E[H\E[J, cr=^M, cub1=^H,
<       cud1=\E[B, cuf1=\E[C, cup=\E[%i%p1%d;%p2%dH, 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, home=\E[H, hpa=\E[%i%p1%dG, ht=^I,
<       hts=\EH, ich=\E[%p1%d@, ich1=\E[@, il=\E[%p1%dL, il1=\E[L,
<       ind=^J, invis=\E[8m, kbs=^H, kcub1=\E[D, kcud1=\E[B,
<       kcuf1=\E[C, kcuu1=\E[A, kdch1=\E[3~, kend=\E[4~, kf1=\E[[A,
---
>       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,
19c21,22
<       rc=\E8, rev=\E[7m, ri=\EM, rmir=\E[4l, rmpch=\E[10m,
---
>       rc=\E8, rev=\E[7m, ri=\EM, rmacs=\E[10m,
>       rmcup=\E[2J\E[?47l\E8, rmir=\E[4l, rmpch=\E[10m,
23,24c26,28
<       sgr0=\E[0;10m, smir=\E[4h, smpch=\E[11m, smso=\E[7m,
<       smul=\E[4m, u6=\E[%i%d;%dR, u7=\E[6n, u9=\E[c,
---
>       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,


Clearly, there are many differences between the infocmp reports for Debian 3.0
and 3.1.  I don't know which of all those escape codes (?) is the root cause of
the problem, but one (or more) of them must be.  I am hesitant to take
/etc/terminfo/c/cygwin on a Debian 3.0 machine and blindly step on its successor
in my Debian 3.1 machines.


Does anybody know how to fix this problem?  Do I need to figure out which
package the terminfo stuff comes from and file a bug report?


TIA,

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

[Brian Dessent]

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

[David Christensen]

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

[René Berber]

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

[David Christensen]

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:

    dpchrist@p166v:~$ 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/

Re: Cygwin, ssh, and top

[David Rothenberger]

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:
> 
>     dpchrist@p166v:~$ 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 Rothenberger                spammer? -> spam@daveroth.dyndns.org
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 Christensen]

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

[Chris Taylor]

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 10000 -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

[Larry Hall (Cygwin)]

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 10000 -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/

rxvt as Bash login console

[David Christensen]

Chris Taylor wrote:
> 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 10000 -sr +sk -si -sw -fg Green -bg Black -e /bin/bash --logi
> n -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.

Interesting.  But, I ran across some issues:

1.  The font looks like a scalable font; I prefer the 7x12 bit-mapped
    font so that I can put six consoles on my desktop (1280x1024) and
    the stroke width makes the characters legible.  "man rxvt" and
    playing around with the "-fn" (7x14, 7x13, 7x12) option didn't
    produce a desirable result.  Nor did Shift+KP_Add or
    Shift+KP_Minus. "locate font" led me to
    /usr/share/groff/1.18.1/font, but grep'ing for "7x14" found
    nothing.  Is there a way I can get the 7x12 bit-mapped font in
    rxvt?

2.  It looks like there's a slight problem with the rxvt man page:

        dpchrist@p42800e:~$ man rxvt
        /usr/bin/tbl:<standard input>:310: `.' not last character on lin
e
        /usr/bin/tbl:<standard input>:310: giving up on this table

    Looking at the same page using cmd.exe./Bash, the error message
    flashes by just before the man page is displayed, and is gone after
    exiting the man page.

3.  Copying from the rxvt console to the Windows (XP Professional SP2)
    clipboard using Ctrl+C causes a new prompt to be displayed.  Is
    there a way to avoid/ prevent this?  "man rxvt" "/copy" reveals
    nothing.

4.  How do I paste from the clipboard to rxvt?  "man rxvt" "/paste"
    reveals nothing.

5.  The rxvt consoles appear to be always on top.  How do I turn this
    mode off?


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: rxvt as Bash login console

[Brian Dessent]

David Christensen wrote:

> 1.  The font looks like a scalable font; I prefer the 7x12 bit-mapped
>     font so that I can put six consoles on my desktop (1280x1024) and
>     the stroke width makes the characters legible.  "man rxvt" and
>     playing around with the "-fn" (7x14, 7x13, 7x12) option didn't
>     produce a desirable result.  Nor did Shift+KP_Add or
>     Shift+KP_Minus. "locate font" led me to
>     /usr/share/groff/1.18.1/font, but grep'ing for "7x14" found
>     nothing.  Is there a way I can get the 7x12 bit-mapped font in
>     rxvt?

Try -fn "FixedSys".  There might be other ways to get the bitmap fonts
by name.  There are a ton of .fon files in the %WINDIR%\Fonts directory,
you can try specifying them by name.  Maybe -fn "8514fix".

The above applies to W11 mode.  If you're using X11 mode then you'll
have to use a proper X11 font specifier such as
"-misc-fixed-medium-r-*-*-12-*-*-*-*-*-*-*".

Personally, I can't stand the bitmapped fonts.  Your objection seems to
revolve around the size, but you can change that.  I use -fn "Lucida
Console-11" and find it the best of all the monospaced fonts.  Vary the
number to change the size.

> 2.  It looks like there's a slight problem with the rxvt man page:
> 
>         dpchrist@p42800e:~$ man rxvt
>         /usr/bin/tbl:<standard input>:310: `.' not last character on lin
> e
>         /usr/bin/tbl:<standard input>:310: giving up on this table
> 
>     Looking at the same page using cmd.exe./Bash, the error message
>     flashes by just before the man page is displayed, and is gone after
>     exiting the man page.

The rxvt manpage has always had problems.  I don't think the above
warning detracts from the ability to read the output though.

> 3.  Copying from the rxvt console to the Windows (XP Professional SP2)
>     clipboard using Ctrl+C causes a new prompt to be displayed.  Is
>     there a way to avoid/ prevent this?  "man rxvt" "/copy" reveals
>     nothing.

That's because ^C is not the copy command in rxvt.  (It's being
interpreted by bash as "abort this command".)  In rxvt you don't do
anything to copy, it's done as soon as you highlight.

> 4.  How do I paste from the clipboard to rxvt?  "man rxvt" "/paste"
>     reveals nothing.

Press the middle mouse button or shift-Ins to paste.  (section TEXT
SELECTION AND INSERTION in the manpage.)

> 5.  The rxvt consoles appear to be always on top.  How do I turn this
>     mode off?

I've never had that happen.  Are you using W11 (native) or X11?

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

[Chris Taylor]

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: rxvt as Bash login console

[Chris Taylor]

David Christensen wrote:
> 
> Interesting.  But, I ran across some issues:
> 
> 1.  The font looks like a scalable font; I prefer the 7x12 bit-mapped
>     font so that I can put six consoles on my desktop (1280x1024) and
>     the stroke width makes the characters legible.  "man rxvt" and
>     playing around with the "-fn" (7x14, 7x13, 7x12) option didn't
>     produce a desirable result.  Nor did Shift+KP_Add or
>     Shift+KP_Minus. "locate font" led me to
>     /usr/share/groff/1.18.1/font, but grep'ing for "7x14" found
>     nothing.  Is there a way I can get the 7x12 bit-mapped font in
>     rxvt?
> 

The standard cmd.exe font options are related to raster fonts - I've no 
idea if you can get rxvt to use these.
However, lucida console size 12 is also 7x12 - so this should work.. Not 
sure how you'd specify it, beyond that you use -fn.
Can't find the option to set the size, but I imagine that is in the manpage.

> 2.  It looks like there's a slight problem with the rxvt man page:
> 
>         dpchrist@p42800e:~$ man rxvt
>         /usr/bin/tbl:<standard input>:310: `.' not last character on lin
> e
>         /usr/bin/tbl:<standard input>:310: giving up on this table
> 
>     Looking at the same page using cmd.exe./Bash, the error message
>     flashes by just before the man page is displayed, and is gone after
>     exiting the man page.

I get the same, but I don't know how it affects the page - this needs to 
be flagged to the rxvt maintainer.
It's a lot better than it used to be though (see archives)

> 
> 3.  Copying from the rxvt console to the Windows (XP Professional SP2)
>     clipboard using Ctrl+C causes a new prompt to be displayed.  Is
>     there a way to avoid/ prevent this?  "man rxvt" "/copy" reveals
>     nothing.

Unix style.
Select (left click & drag) to copy to clipboard. Use ctrl-v/shift-ins as 
normal in other apps to paste.
Middle-click to paste in rxvt.
Ctrl-C is supposed to abort the current command, so this is normal 
behaviour.

> 
> 4.  How do I paste from the clipboard to rxvt?  "man rxvt" "/paste"
>     reveals nothing.

See above.

> 
> 5.  The rxvt consoles appear to be always on top.  How do I turn this
>     mode off?
> 

I can't say I've ever had this problem... Did you copy my cygwin.bat 
verbatim, or make changes to it?

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]

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

[David Christensen]

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:

dpchrist@p42800e:~/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:

    dpchrist@p166v:~$ 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: rxvt as Bash login console

[David Christensen]

I wrote:
> 3.  Copying from the rxvt console ....
> 4.  How do I paste from the clipboard to rxvt?  ...

Chris Taylor wrote:
> Unix style.

Yup.


> I can't say I've ever had this problem... Did you copy my cygwin.bat 
> verbatim, or make changes to it?

Uh, yeah!  (Quickly find previous message, cut and paste into batch file, run
it, test).  Yeah, verbatim!


But, the problem isn't there today...  If and when I can reproduce it, I'll post
the procedure.


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: rxvt as Bash login console

[David Christensen]

Brian Dessent wrote:
> I use -fn "Lucida Console-11...

Yes, that's better.  :-)  But, I still like Cygwin Bash's use of gray for text,
white for bolding, cyan (?) in perldoc pages, etc., and the way I can control
things via the DOS box Properties.  But, I have and will use rxvt for "top" on
Debian 3.1 until the extraneous newline issue gets fixed.


> (section TEXT SELECTION AND INSERTION in the manpage.)

Ahh...  I didn't RTFM thoroughly enough; my bad.  :-(


>> 5.  The rxvt consoles appear to be always on top.  How do I turn this
>>     mode off?
> I've never had that happen.

Of course; it only does it to idiots -- er, new rxvt users.  ;-)  Better yet,
it's not doing it today.


> Are you using W11 (native) or X11?

Hmmm...  Not sure.  I don't believe I have Cygwin X11 installed.  Does that
answer your question?  cygcheck.out follows just in case.


Thanks!

David



--
Cygwin Configuration Diagnostics
Current System Time: Mon Oct 17 18:07:54 2005

Windows XP Professional Ver 5.1 Build 2600 Service Pack 2

Path:	C:\cygwin\usr\local\bin
	C:\cygwin\bin
	C:\cygwin\bin
	C:\cygwin\usr\X11R6\bin
	c:\WINDOWS\system32
	c:\WINDOWS
	c:\WINDOWS\System32\Wbem
	C:\cygwin\usr\sbin

Output from C:\cygwin\bin\id.exe (nontsec)
UID: 1003(dpchrist) GID: 513(None)
0(root)             513(None)           544(Administrators) 545(Users)

Output from C:\cygwin\bin\id.exe (ntsec)
UID: 1003(dpchrist) GID: 513(None)
0(root)             513(None)           544(Administrators) 545(Users)

SysDir: C:\WINDOWS\system32
WinDir: C:\WINDOWS

USER = `dpchrist'
PWD = `/home/dpchrist'
HOME = `/home/dpchrist'
MAKE_MODE = `unix'

HOMEPATH = `\Documents and Settings\dpchrist'
MANPATH = `:/home/dpchrist/local/man'
APPDATA = `C:\Documents and Settings\dpchrist\Application Data'
HOSTNAME = `p42800e'
TERM = `cygwin'
PROCESSOR_IDENTIFIER = `x86 Family 15 Model 3 Stepping 3, GenuineIntel'
WINDIR = `C:\WINDOWS'
OLDPWD = `/usr/bin'
USERDOMAIN = `P42800E'
OS = `Windows_NT'
ALLUSERSPROFILE = `C:\Documents and Settings\All Users'
TEMP = `/cygdrive/c/DOCUME~1/dpchrist/LOCALS~1/Temp'
COMMONPROGRAMFILES = `C:\Program Files\Common Files'
PROCESSOR_LEVEL = `15'
FTP_PASSIVE = `1'
FP_NO_HOST_CHECK = `NO'
SYSTEMDRIVE = `C:'
EDITOR = `vim'
LANG = `C'
USERPROFILE = `C:\Documents and Settings\dpchrist'
CLIENTNAME = `Console'
PS1 = `\u@\h:\w\$ '
LOGONSERVER = `\\P42800E'
PROCESSOR_ARCHITECTURE = `x86'
!C: = `C:\cygwin\bin'
HISTCONTROL = `ignoredups'
SHLVL = `1'
OSTYPE = `cygwin'
PATHEXT = `.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH'
HOMEDRIVE = `C:'
PROMPT = `$P$G'
COMSPEC = `C:\WINDOWS\system32\cmd.exe'
LESS = `-R'
TMP = `/cygdrive/c/DOCUME~1/dpchrist/LOCALS~1/Temp'
SYSTEMROOT = `C:\WINDOWS'
PRINTER = `HP LaserJet 4'
PROCESSOR_REVISION = `0303'
INFOPATH = `/usr/local/info:/usr/share/info:/usr/info:'
PROGRAMFILES = `C:\Program Files'
NUMBER_OF_PROCESSORS = `2'
SESSIONNAME = `Console'
COMPUTERNAME = `P42800E'
_ = `/usr/bin/cygcheck'
POSIXLY_CORRECT = `1'

HKEY_CURRENT_USER\Software\Cygnus Solutions
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\mounts v2
HKEY_CURRENT_USER\Software\Cygnus Solutions\Cygwin\Program Options
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
  (default) = `/cygdrive'
  cygdrive flags = 0x00000020
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
  (default) = `C:\cygwin'
  flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
  (default) = `C:\cygwin/bin'
  flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
  (default) = `C:\cygwin/lib'
  flags = 0x00000008
HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\Program Options

a:  fd             N/A    N/A                    
c:  hd  NTFS     76316Mb   9% CP CS UN PA FC     
d:  cd             N/A    N/A                    
e:  hd  NTFS    190779Mb  68% CP CS UN PA FC     DATA
f:  hd  NTFS    238472Mb  89% CP CS UN PA FC     GHOST_250GB

C:\cygwin      /          system  textmode
C:\cygwin/bin  /usr/bin   system  textmode
C:\cygwin/lib  /usr/lib   system  textmode
.              /cygdrive  system  textmode,cygdrive

Found: C:\cygwin\bin\awk.exe
Found: C:\cygwin\bin\bash.exe
Found: C:\cygwin\bin\cat.exe
Found: C:\cygwin\bin\cp.exe
Not Found: cpp (good!)
Found: C:\cygwin\bin\find.exe
Not Found: gcc
Not Found: gdb
Found: C:\cygwin\bin\grep.exe
Not Found: ld
Found: C:\cygwin\bin\ls.exe
Found: C:\cygwin\bin\make.exe
Found: C:\cygwin\bin\mv.exe
Found: C:\cygwin\bin\rm.exe
Found: C:\cygwin\bin\sed.exe
Found: C:\cygwin\bin\sh.exe
Found: C:\cygwin\bin\tar.exe

   56k 2005/07/09 C:\cygwin\bin\cygbz2-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygbz2-1.dll" v0.0 ts=2005/7/8 22:09
   18k 2004/07/06 C:\cygwin\bin\cygcharset-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygcharset-1.dll" v0.0 ts=2004/7/6 11:09
    7k 2003/10/19 C:\cygwin\bin\cygcrypt-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygcrypt-0.dll" v0.0 ts=2003/10/19 0:57
 1109k 2005/10/11 C:\cygwin\bin\cygcrypto-0.9.7.dll - os=4.0 img=1.0 sys=4.0
                  "cygcrypto-0.9.7.dll" v0.0 ts=2005/10/11 5:57
 1047k 2005/10/11 C:\cygwin\bin\cygcrypto-0.9.8.dll - os=4.0 img=1.0 sys=4.0
                  "cygcrypto-0.9.8.dll" v0.0 ts=2005/10/11 5:47
  895k 2004/04/28 C:\cygwin\bin\cygdb-4.2.dll - os=4.0 img=1.0 sys=4.0
                  "cygdb-4.2.dll" v0.0 ts=2004/4/27 8:31
  965k 2005/05/14 C:\cygwin\bin\cygdb-4.3.dll - os=4.0 img=1.0 sys=4.0
                  "cygdb-4.3.dll" v0.0 ts=2005/5/14 5:37
 1156k 2004/04/28 C:\cygwin\bin\cygdb_cxx-4.2.dll - os=4.0 img=1.0 sys=4.0
                  "cygdb_cxx-4.2.dll" v0.0 ts=2004/4/27 8:35
 1240k 2005/05/14 C:\cygwin\bin\cygdb_cxx-4.3.dll - os=4.0 img=1.0 sys=4.0
                  "cygdb_cxx-4.3.dll" v0.0 ts=2005/5/14 5:41
  174k 2004/10/14 C:\cygwin\bin\cygexpat-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygexpat-0.dll" v0.0 ts=2004/10/14 1:34
   40k 2005/09/29 C:\cygwin\bin\cygform-8.dll - os=4.0 img=1.0 sys=4.0
                  "cygform-8.dll" v0.0 ts=2005/9/28 19:15
   45k 2001/04/25 C:\cygwin\bin\cygform5.dll - os=4.0 img=1.0 sys=4.0
                  "cygform5.dll" v0.0 ts=2001/4/24 22:28
   35k 2002/01/09 C:\cygwin\bin\cygform6.dll - os=4.0 img=1.0 sys=4.0
                  "cygform6.dll" v0.0 ts=2002/1/8 22:03
   48k 2003/08/09 C:\cygwin\bin\cygform7.dll - os=4.0 img=1.0 sys=4.0
                  "cygform7.dll" v0.0 ts=2003/8/9 2:25
   28k 2003/07/20 C:\cygwin\bin\cyggdbm-3.dll - os=4.0 img=1.0 sys=4.0
                  "cyggdbm-3.dll" v0.0 ts=2003/7/20 0:58
   30k 2003/08/11 C:\cygwin\bin\cyggdbm-4.dll - os=4.0 img=1.0 sys=4.0
                  "cyggdbm-4.dll" v0.0 ts=2003/8/10 19:12
   19k 2003/03/22 C:\cygwin\bin\cyggdbm.dll - os=4.0 img=1.0 sys=4.0
                  "cyggdbm.dll" v0.0 ts=2002/2/19 19:05
   15k 2003/07/20 C:\cygwin\bin\cyggdbm_compat-3.dll - os=4.0 img=1.0 sys=4.0
                  "cyggdbm_compat-3.dll" v0.0 ts=2003/7/20 1:00
   15k 2003/08/11 C:\cygwin\bin\cyggdbm_compat-4.dll - os=4.0 img=1.0 sys=4.0
                  "cyggdbm_compat-4.dll" v0.0 ts=2003/8/10 19:13
   17k 2001/06/28 C:\cygwin\bin\cyghistory4.dll - os=4.0 img=1.0 sys=4.0
                  "cyghistory4.dll" v0.0 ts=2001/1/6 20:34
   29k 2003/08/10 C:\cygwin\bin\cyghistory5.dll - os=4.0 img=1.0 sys=4.0
                  "cyghistory5.dll" v0.0 ts=2003/8/10 16:16
   24k 2005/07/29 C:\cygwin\bin\cyghistory6.dll - os=4.0 img=1.0 sys=4.0
                  "cyghistory6.dll" v0.0 ts=2005/7/28 20:57
  991k 2004/07/06 C:\cygwin\bin\cygiconv-2.dll - os=4.0 img=1.0 sys=4.0
                  "cygiconv-2.dll" v0.0 ts=2004/7/6 11:10
   22k 2001/12/13 C:\cygwin\bin\cygintl-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygintl-1.dll" v0.0 ts=2001/12/13 1:28
   37k 2003/08/10 C:\cygwin\bin\cygintl-2.dll - os=4.0 img=1.0 sys=4.0
                  "cygintl-2.dll" v0.0 ts=2003/8/10 14:50
   54k 2004/07/06 C:\cygwin\bin\cygintl-3.dll - os=4.0 img=1.0 sys=4.0
                  "cygintl-3.dll" v0.0 ts=2004/7/6 10:51
   21k 2001/06/20 C:\cygwin\bin\cygintl.dll - os=4.0 img=1.0 sys=4.0
                  "cygintl.dll" v0.0 ts=2001/6/20 10:09
   68k 2005/09/07 C:\cygwin\bin\cygmagic-1.dll - os=4.0 img=1.0 sys=4.0
                  "cygmagic-1.dll" v0.0 ts=2005/9/7 3:21
   21k 2005/09/29 C:\cygwin\bin\cygmenu-8.dll - os=4.0 img=1.0 sys=4.0
                  "cygmenu-8.dll" v0.0 ts=2005/9/28 19:15
   26k 2001/04/25 C:\cygwin\bin\cygmenu5.dll - os=4.0 img=1.0 sys=4.0
                  "cygmenu5.dll" v0.0 ts=2001/4/24 22:27
   20k 2002/01/09 C:\cygwin\bin\cygmenu6.dll - os=4.0 img=1.0 sys=4.0
                  "cygmenu6.dll" v0.0 ts=2002/1/8 22:03
   29k 2003/08/09 C:\cygwin\bin\cygmenu7.dll - os=4.0 img=1.0 sys=4.0
                  "cygmenu7.dll" v0.0 ts=2003/8/9 2:25
   21k 2004/10/22 C:\cygwin\bin\cygminires.dll - os=4.0 img=1.0 sys=4.0
                  "cygminires.dll" v0.0 ts=2004/10/22 13:28
   67k 2005/09/29 C:\cygwin\bin\cygncurses++-8.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses++-8.dll" v0.0 ts=2005/9/28 19:16
  156k 2001/04/25 C:\cygwin\bin\cygncurses++5.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses++5.dll" v0.0 ts=2001/4/24 22:29
  175k 2002/01/09 C:\cygwin\bin\cygncurses++6.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses++6.dll" v0.0 ts=2002/1/8 22:03
  226k 2005/09/29 C:\cygwin\bin\cygncurses-8.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses-8.dll" v0.0 ts=2005/9/28 19:02
  226k 2001/04/25 C:\cygwin\bin\cygncurses5.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses5.dll" v0.0 ts=2001/4/24 22:17
  202k 2002/01/09 C:\cygwin\bin\cygncurses6.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses6.dll" v0.0 ts=2002/1/8 22:03
  224k 2003/08/09 C:\cygwin\bin\cygncurses7.dll - os=4.0 img=1.0 sys=4.0
                  "cygncurses7.dll" v0.0 ts=2003/8/9 2:24
   11k 2005/09/29 C:\cygwin\bin\cygpanel-8.dll - os=4.0 img=1.0 sys=4.0
                  "cygpanel-8.dll" v0.0 ts=2005/9/28 19:15
   15k 2001/04/25 C:\cygwin\bin\cygpanel5.dll - os=4.0 img=1.0 sys=4.0
                  "cygpanel5.dll" v0.0 ts=2001/4/24 22:27
   12k 2002/01/09 C:\cygwin\bin\cygpanel6.dll - os=4.0 img=1.0 sys=4.0
                  "cygpanel6.dll" v0.0 ts=2002/1/8 22:03
   19k 2003/08/09 C:\cygwin\bin\cygpanel7.dll - os=4.0 img=1.0 sys=4.0
                  "cygpanel7.dll" v0.0 ts=2003/8/9 2:24
  176k 2005/09/06 C:\cygwin\bin\cygpcre-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygpcre-0.dll" v0.0 ts=2005/9/6 13:49
  299k 2005/09/06 C:\cygwin\bin\cygpcrecpp-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygpcrecpp-0.dll" v0.0 ts=2005/9/6 14:26
    6k 2005/09/06 C:\cygwin\bin\cygpcreposix-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygpcreposix-0.dll" v0.0 ts=2005/9/6 14:26
 1248k 2005/08/22 C:\cygwin\bin\cygperl5_8.dll - os=4.0 img=1.0 sys=4.0
                  "cygperl5_8.dll" v0.0 ts=2005/8/22 13:06
   22k 2002/06/09 C:\cygwin\bin\cygpopt-0.dll - os=4.0 img=1.0 sys=4.0
                  "cygpopt-0.dll" v0.0 ts=2002/6/8 22:45
  108k 2001/06/28 C:\cygwin\bin\cygreadline4.dll - os=4.0 img=1.0 sys=4.0
                  "cygreadline4.dll" v0.0 ts=2001/1/6 20:34
  148k 2003/08/10 C:\cygwin\bin\cygreadline5.dll - os=4.0 img=1.0 sys=4.0
                  "cygreadline5.dll" v0.0 ts=2003/8/10 16:16
  144k 2005/07/29 C:\cygwin\bin\cygreadline6.dll - os=4.0 img=1.0 sys=4.0
                  "cygreadline6.dll" v0.0 ts=2005/7/28 20:57
  231k 2005/10/11 C:\cygwin\bin\cygssl-0.9.7.dll - os=4.0 img=1.0 sys=4.0
                  "cygssl-0.9.7.dll" v0.0 ts=2005/10/11 5:57
  215k 2005/10/11 C:\cygwin\bin\cygssl-0.9.8.dll - os=4.0 img=1.0 sys=4.0
                  "cygssl-0.9.8.dll" v0.0 ts=2005/10/11 5:47
   65k 2005/08/23 C:\cygwin\bin\cygz.dll - os=4.0 img=1.0 sys=4.0
                  "cygz.dll" v0.0 ts=2005/8/22 19:03
 1265k 2005/07/03 C:\cygwin\bin\cygwin1.dll - os=4.0 img=1.0 sys=4.0
                  "cygwin1.dll" v0.0 ts=2005/7/2 17:30
    Cygwin DLL version info:
        DLL version: 1.5.18
        DLL epoch: 19
        DLL bad signal mask: 19005
        DLL old termios: 5
        DLL malloc env: 28
        API major: 0
        API minor: 132
        Shared data: 4
        DLL identifier: cygwin1
        Mount registry: 2
        Cygnus registry name: Cygnus Solutions
        Cygwin registry name: Cygwin
        Program options name: Program Options
        Cygwin mount registry name: mounts v2
        Cygdrive flags: cygdrive flags
        Cygdrive prefix: cygdrive prefix
        Cygdrive default prefix: 
        Build date: Sat Jul 2 20:30:04 EDT 2005
        Shared id: cygwin1S4


Service             : sshd
Display name        : CYGWIN sshd
Current State       : Running
Controls Accepted   : Stop
Command             : /usr/sbin/sshd -D
stdin path          : /dev/null
stdout path         : /var/log/sshd.log
stderr path         : /var/log/sshd.log
Environment         : CYGWIN="ntsec" 
Process Type        : Own Process
Startup             : Automatic
Account             : LocalSystem


Cygwin Package Information
Last downloaded files to: C:\cygwin\setup
Last downloaded files from: http://planetmirror.com/pub/sourceware/cygwin

Package              Version
_update-info-dir     00323-1
alternatives         1.3.20a-1
ash                  20040127-3
base-files           3.6-1
base-passwd          2.2-1
bash                 3.0-11
bzip2                1.0.3-1
clear                1.0-2
coreutils            5.3.0-9
crypt                1.1-1
cvs                  1.11.17-1
cvsutils             0.2.3-1
cygrunsrv            1.10-1
cygutils             1.2.9-1
cygwin               1.5.18-1
cygwin-doc           1.4-3
dejagnu              20021217-2
diffutils            2.8.7-1
editrights           1.01-1
expat                1.95.8-1
expect               20030128-1
file                 4.15-3
findutils            4.2.25-2
gawk                 3.1.5-1
gcc-testsuite        3.4.4-1
gdbm                 1.8.3-7
grep                 2.5.1a-2
groff                1.18.1-2
gzip                 1.3.5-1
indent               2.2.9-1
less                 381-1
libbz2_1             1.0.3-1
libcharset1          1.9.2-1
libdb4.2             4.2.52-1
libdb4.3             4.3.28-1
libgdbm              1.8.0-5
libgdbm-devel        1.8.3-7
libgdbm3             1.8.3-3
libgdbm4             1.8.3-7
libiconv             1.9.2-1
libiconv2            1.9.2-1
libintl              0.10.38-3
libintl1             0.10.40-1
libintl2             0.12.1-3
libintl3             0.14.1-1
libncurses5          5.2-1
libncurses6          5.2-8
libncurses7          5.3-4
libncurses8          5.4-4
libpcre0             6.3-1
libpopt0             1.6.4-4
libreadline4         4.1-2
libreadline5         4.3-5
libreadline6         5.0-4
login                1.9-7
make                 3.80-1
man                  1.5p-1
minires              1.00-1
mktemp               1.5-3
ncurses              5.4-4
openssh              4.2p1-1
openssl              0.9.8a-1
openssl097           0.9.7h-1
perl                 5.8.7-4
perl_manpages        5.8.7-4
ping                 1.0-1
rebase               2.4.2-1
rsync                2.6.6-1
rxvt                 2.7.10-6
sed                  4.1.4-1
tar                  1.15.1-2
tcltk                20030901-1
termcap              20050421-1
terminfo             5.4_20041009-1
texinfo              4.8-1
time                 1.7-1
vim                  6.3-1
wget                 1.10.1-2
which                1.7-1
whois                4.7.8-1
zlib                 1.2.3-1
Use -h to see help about each section


--
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: rxvt as Bash login console

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to David Christensen on 10/17/2005 7:52 PM:
> 
> Yes, that's better.  :-)  But, I still like Cygwin Bash's use of gray for text,
> white for bolding, cyan (?) in perldoc pages, etc., and the way I can control
> things via the DOS box Properties.

$ cat ~/.Xdefaults
! Fix rxvt to mimic windows console coloring
XTerm*background: black
XTerm*foreground: gray
XTerm*geometry: 80x50
XTerm*jumpScroll: True
XTerm*scrollBar_right: True

> 
> C:\cygwin      /          system  textmode
> C:\cygwin/bin  /usr/bin   system  textmode
> C:\cygwin/lib  /usr/lib   system  textmode

Not a good idea.  /bin, /lib, /usr/bin, and /usr/lib should generally be
binary mounts for best behavior.

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDVFyP84KuGfSFAYARAnE0AJ9SIPoPa84Wurkrc96Z7YiS4yOppgCffKin
4RqJH1f7b83W10zbMjlHh3I=
=ZeLO
-----END PGP SIGNATURE-----

--
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: rxvt as Bash login console

[Brian Dessent]

David Christensen wrote:

> Yes, that's better.  :-)  But, I still like Cygwin Bash's use of gray for text,
> white for bolding, cyan (?) in perldoc pages, etc., and the way I can control
> things via the DOS box Properties.  But, I have and will use rxvt for "top" on
> Debian 3.1 until the extraneous newline issue gets fixed.

You can configure rxvt to do all that too.

       colorn: colour
              Use the specified colour for the colour value n, where 0-7
              corresponds  to  low-intensity  (normal)  colours and 8-15
              corresponds to high-intensity (bold =  bright  foreground,
              blink  =  bright background) colours.  The canonical names
              are as follows: 0=black, 1=red, 2=green, 3=yellow, 4=blue,
              5=magenta,  6=cyan,  7=white,  but the actual colour names
              used are listed in the COLORS AND GRAPHICS section.

       colorBD: colour
              Use the specified colour to display bold  characters  when
              the foreground colour is the default.

       colorUL: colour
              Use  the specified colour to display underlined characters
              when the foreground colour is the default.

       colorRV: colour
              Use the specified colour as  the  background  for  reverse
              video characters.

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: rxvt as Bash login console

[David Christensen]

Eric Blake wrote:
> $ cat ~/.Xdefaults
> ! Fix rxvt to mimic windows console coloring
> XTerm*background: black
> XTerm*foreground: gray
> XTerm*geometry: 80x50
> XTerm*jumpScroll: True
> XTerm*scrollBar_right: True

"man rxvt" and this page were helpful:

    http://www.xfree86.org/current/xterm.1.html


I was able to reduce my rxvt.bat file to this:

    dpchrist@p42800e:~$ cat rxvt.bat 
    @echo off
    rem $Id: rxvt.bat,v 1.1 2005/10/18 04:17:23 dpchrist Exp $
    C:
    chdir C:\cygwin\bin
    rxvt -fn "Lucida Console-11" -e /bin/bash --login -i


Here is my .Xdefaults:

    dpchrist@p42800e:~$ cat .Xdefaults 
    ! $Id: .Xdefaults,v 1.1 2005/10/18 04:17:23 dpchrist Exp $
    XTerm*background: black
    XTerm*foreground: gray
    XTerm*colorBD: white
    XTerm*colorUL: cyan
    XTerm*saveLines: 10000
    XTerm*scrollBar_right: True
    XTerm*scrollTtyKeypress: True
    XTerm*scrollTtyOutput: True


>> C:\cygwin      /          system  textmode
>> C:\cygwin/bin  /usr/bin   system  textmode
>> C:\cygwin/lib  /usr/lib   system  textmode
> Not a good idea.  /bin, /lib, /usr/bin, and /usr/lib should generally
> be binary mounts for best behavior.

Okay.  I ran Cygwin setup and changed the "Default Text File Type" to "Unix/
binary":

    dpchrist@p42800e:~$ cygcheck -s -v -r | grep mode
    C:\cygwin      /          system  binmode
    C:\cygwin/bin  /usr/bin   system  binmode
    C:\cygwin/lib  /usr/lib   system  binmode
    .              /cygdrive  system  binmode,cygdrive


It looks like CVS is now checking out text files using Unix line endings.  I'm
sure I'll find other differences as time goes on.  Hopefully this won't be too
painful of a change...


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: rxvt as Bash login console

[Igor Pechtchanski]

On Mon, 17 Oct 2005, David Christensen wrote:

> Okay.  I ran Cygwin setup and changed the "Default Text File Type" to
> "Unix/ binary":
>
>     dpchrist@p42800e:~$ cygcheck -s -v -r | grep mode
>     C:\cygwin      /          system  binmode
>     C:\cygwin/bin  /usr/bin   system  binmode
>     C:\cygwin/lib  /usr/lib   system  binmode
>     .              /cygdrive  system  binmode,cygdrive
>
> It looks like CVS is now checking out text files using Unix line
> endings.  I'm sure I'll find other differences as time goes on.
> Hopefully this won't be too painful of a change...

FWIW, you can mount individual directories in text mode without much
trouble -- see "man mount".
HTH,
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

--
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: rxvt as Bash login console

[Karl M]

>From: "David Christensen"
>CC: "'Eric Blake'"
>Subject: RE: rxvt as Bash login console
>Date: Mon, 17 Oct 2005 21:25:12 -0700
>
>Eric Blake wrote:
> > $ cat ~/.Xdefaults
> > ! Fix rxvt to mimic windows console coloring
> > XTerm*background: black
> > XTerm*foreground: gray
> > XTerm*geometry: 80x50
> > XTerm*jumpScroll: True
> > XTerm*scrollBar_right: True
>
>"man rxvt" and this page were helpful:
>
>     http://www.xfree86.org/current/xterm.1.html
>
>
>I was able to reduce my rxvt.bat file to this:
>
>     dpchrist@p42800e:~$ cat rxvt.bat
>     @echo off
>     rem $Id: rxvt.bat,v 1.1 2005/10/18 04:17:23 dpchrist Exp $
>     C:
>     chdir C:\cygwin\bin
>     rxvt -fn "Lucida Console-11" -e /bin/bash --login -i
>
>
>Here is my .Xdefaults:
>
>     dpchrist@p42800e:~$ cat .Xdefaults
>     ! $Id: .Xdefaults,v 1.1 2005/10/18 04:17:23 dpchrist Exp $
>     XTerm*background: black
>     XTerm*foreground: gray
>     XTerm*colorBD: white
>     XTerm*colorUL: cyan
>     XTerm*saveLines: 10000
>     XTerm*scrollBar_right: True
>     XTerm*scrollTtyKeypress: True
>     XTerm*scrollTtyOutput: True
>
>
> >> C:\cygwin      /          system  textmode
> >> C:\cygwin/bin  /usr/bin   system  textmode
> >> C:\cygwin/lib  /usr/lib   system  textmode
> > Not a good idea.  /bin, /lib, /usr/bin, and /usr/lib should generally
> > be binary mounts for best behavior.
>
>Okay.  I ran Cygwin setup and changed the "Default Text File Type" to 
>"Unix/
>binary":
>
>     dpchrist@p42800e:~$ cygcheck -s -v -r | grep mode
>     C:\cygwin      /          system  binmode
>     C:\cygwin/bin  /usr/bin   system  binmode
>     C:\cygwin/lib  /usr/lib   system  binmode
>     .              /cygdrive  system  binmode,cygdrive
>
>
>It looks like CVS is now checking out text files using Unix line endings.  
>I'm
>sure I'll find other differences as time goes on.  Hopefully this won't be 
>too
>painful of a change...
>
>
>Thanks!
>
>David
>
Recent versions of CVSNT now pwwc (play well with Cygwin). That is, if you 
set CVS_RSH to 'C:\Cygwin\bib\ssh.exe' you can use Cygwin/OpenSSH (ssh, 
ssh-agent, etc.) for your connection. I started using it for better 
interoperability with WinCvs, but this also gives you DOS line endings no 
mater what your mounts look like (which may or may not be what you want).

HTH,

...Karl



--
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/