Re: screen

2005-04-20 Thread Christopher Faylor
On Wed, Apr 20, 2005 at 05:18:09PM -0400, [EMAIL PROTECTED] wrote: >I'm going to try to build and package screen for Cygwin. It's such a >useful program, I just have to try. > >screen 4.0.2 won't compile OOTB in Cygwin: > >gcc -c -I. -I.-g -O2 misc.c >misc.c: In function `xsetenv': >misc.c:61

Re: screen

2005-04-20 Thread Andrew Schulman
> > I'm going to try to build and package screen for Cygwin. > > It's such a useful program, I just have to try. > > Could somebody *please* explain to me why screen is in any way useful on a > system with even a semblance of a window manager? I can see the point of > screen on a stripped-down

RE: screen

2005-04-20 Thread elijah wright
Could somebody *please* explain to me why screen is in any way useful on a system with even a semblance of a window manager? I can see the point of screen on a stripped-down text-only system, but when you can open up any number of rxvt+bash's and ALT-TAB between them... ...what am I missing?

RE: screen

2005-04-20 Thread Gary R. Van Sickle
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Schulman.Andrew > > I'm going to try to build and package screen for Cygwin. > It's such a useful program, I just have to try. > Could somebody *please* explain to me why screen is in any way u

Re: screen

2005-04-20 Thread Andrew Schulman
> The major obstacle to porting screen is that you have to understand how > Cygwin handles terminals, which I don't, but maybe you do. If you > understand that, then it should be possible, but if not then I don't > know what to tell you. Well I thought this might be the case. No, I don't underst

Re: screen

2005-04-20 Thread Igor Pechtchanski
On Wed, 20 Apr 2005, Schulman.Andrew wrote: > I'm going to try to build and package screen for Cygwin. It's such a > useful program, I just have to try. > > screen 4.0.2 won't compile OOTB in Cygwin: > > gcc -c -I. -I.-g -O2 misc.c > misc.c: In function `xsetenv': > misc.c:619: error: too few

Re: ITP: typespeed-0.4.4

2005-04-20 Thread Corinna Vinschen
On Apr 20 23:50, Lapo Luchini wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Corinna Vinschen wrote: > > > No no, it's Debian-approved as you wrote and packaging looks ok, > > AFAICS. Just one question: Is it safe to put the rc file into /etc > > or would there be a good reason to

Re: ITP: typespeed-0.4.4

2005-04-20 Thread Lapo Luchini
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Corinna Vinschen wrote: > No no, it's Debian-approved as you wrote and packaging looks ok, > AFAICS. Just one question: Is it safe to put the rc file into /etc > or would there be a good reason to put this into /etc/defaults/etc > and install via po

Re: ITP: typespeed-0.4.4

2005-04-20 Thread Corinna Vinschen
On Apr 20 23:30, Lapo Luchini wrote: > Lapo Luchini wrote: > > > ...and package is ready. > > > > http://www.lapo.it/cygwin/typespeed-0.4.4-1-src.tar.bz2 > > http://www.lapo.it/cygwin/typespeed-0.4.4-1.tar.bz2 > > BTW: I also tried the network head-to-head playing, and seems to work > ok, for me.

Re: screen

2005-04-20 Thread Harold L Hunt II
Andrew, I tried packaging screen a long time ago, and failed. I got it compiling, but it didn't work correctly. I seem to recall that it really didn't work at all. The major obstacle to porting screen is that you have to understand how Cygwin handles terminals, which I don't, but maybe you do.

Re: ITP: typespeed-0.4.4

2005-04-20 Thread Lapo Luchini
Lapo Luchini wrote: > ...and package is ready. > > http://www.lapo.it/cygwin/typespeed-0.4.4-1-src.tar.bz2 > http://www.lapo.it/cygwin/typespeed-0.4.4-1.tar.bz2 BTW: I also tried the network head-to-head playing, and seems to work ok, for me. If no one else is interested in it I guess I'll put u

Re: screen

2005-04-20 Thread Lapo Luchini
[EMAIL PROTECTED] wrote: >If anyone else has tried and failed to build or package screen for >Cygwin, or if you know anything else about the feasibility of this >little project, I'd appreciate hearing from you. > I found this googling, maybe it's a mirror of what you're seeking: http://www.j10n.

screen

2005-04-20 Thread Schulman . Andrew
I'm going to try to build and package screen for Cygwin. It's such a useful program, I just have to try. screen 4.0.2 won't compile OOTB in Cygwin: gcc -c -I. -I.-g -O2 misc.c misc.c: In function `xsetenv': misc.c:619: error: too few arguments to function `setenv' make: *** [misc.o] Error 1

RE: Vital information for anyone debugging setup.exe

2005-04-20 Thread Dave Korn
Original Message >From: Brian Dessent >Sent: 20 April 2005 10:14 > Dave Korn wrote: > >> Nope, I saw that, but I wanted to fix insight rather than setup, >> because otherwise it's gonna happen again with some other piece of >> software... I'm in the habit of using loadsa debug messages

[PATCH] Uninstall .dll last, reinstall first - final version

2005-04-20 Thread Dave Korn
Well, it builds, and it works, and I've tested it by rolling an installation back-and-forth across quite a large update (the difference between my local mirror set up last september and an up-to-date mirror), which I could do with the old setup and see things fail when it removed the cygwin dll

Re: Request for pkg-config update

2005-04-20 Thread Max Bowsher
Charles Wilson wrote: Max Bowsher wrote: Pkg-config maintainer, please could we have an update? Current is 0.17.2, Cygwin package is 0.15.0. Thanks. Development seemed stalled for so long I thought it was dead. I'll roll an update out soon. Thankyou! :-) Max.

Re: Vital information for anyone debugging setup.exe

2005-04-20 Thread Brian Dessent
Dave Korn wrote: > Nope, I saw that, but I wanted to fix insight rather than setup, because > otherwise it's gonna happen again with some other piece of software... I'm > in the habit of using loadsa debug messages and logging them with dbgview or > similar, and I don't want to accidentally wind

RE: Vital information for anyone debugging setup.exe

2005-04-20 Thread Dave Korn
Original Message >From: Brian Dessent >Sent: 20 April 2005 06:29 > Dave Korn wrote: > >> It would probably be easier simpler and quicker to find the messagebox >> call in the insight source (most of which is just tcl/tk scripting after >> all) and comment it out. > > Perhaps you missed