Re: socat with IP6 support?

On Fri, Jan 17, 2014 at 3:19 PM, Corinna Vinschen wrote: > Our ipv6 stuff is in cygwin/in6.h, which is included by cygwin/in.h, > which in turn is included by netinet/in.h. Ah, that explains it. > We could fetch FreeBSDs netinet/ip6.h. In contrast to Glibc's > netinet/ip6.h it does not include n

Re: Vim under screen screwing up console on close

ee the same thing using less. Less, vim, man...wasn't there another issue recently that involved those? Maybe I'll try that snapshot and see if that helps with this problem at all. On Fri, Jan 17, 2014 at 11:47 AM, Aaron Humphrey wrote: > I recently updated my Cygwin64 insta

Re: socat with IP6 support?

On Fri, Jan 17, 2014 at 12:34 PM, Warren Young wrote: > On 1/17/2014 11:58, Aaron Humphrey wrote: >> >> I had thought that cygwin 1.7 had IPv6 support, > > > It does, to the extent that the underlying Winsock APIs do. Basically, you > want to be on Vista or newer i

Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path

On Fri, May 29, 2009 at 9:16 AM, Larry Hall wrote: > Aaron Humphrey wrote: >> >> So, in the end, reinstalling didn't do much.  And I got a bunch of >> "Cannot open (null) for reading" (error not guaranteed to be >> accurate), usually when it was trying to

Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path

So, in the end, reinstalling didn't do much. And I got a bunch of "Cannot open (null) for reading" (error not guaranteed to be accurate), usually when it was trying to install gzipped man pages or something. (Times like these I wonder why I persist in downloading every cygwin package on the mirro

Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path

On Wed, May 27, 2009 at 10:32 PM, Karl M wrote: > >> Date: Wed, 27 May 2009 21:26:36 -0600 >> Subject: Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path >> From: alfvaen >> You seem to be missing '/usr/bin' and '/usr/lib'. There was talk about some of this changing though in my

Re: Upgrade to cygwin 1.7 seemed to trash bash profile, path

>> You seem to be missing '/usr/bin' and '/usr/lib'. There was talk about >> some of this changing though in my up-to-date installation, I still have >> them so I'm not sure where this stands. In any case, it suggests that >> you may want to try add the following to your '/etc/fstab' file: >> >> c:

Re: Packaging error?

On Fri, Aug 15, 2008 at 6:09 PM, Angelo Graziosi wrote: > > I have seen that both packages 'fltk-demos' and 'sudoku' contain the file > > usr/bin/sudoku.exe > > At the moment I have only 'fltk-demos' installed. What would it happen > if I install also 'sudoku' package? My opinion is that > 'usr/bin

Setup package list duplication and crash

For a while I've been downloading from http://mirrors.dotsrc.org. I switched a few days ago when it started acting strangely. Several packages were displayed as Not Installed--bashdb3, gcc-gm2, libglade, libltdl6, and libploticus. When I clicked on "Skip" to try to install one of them, Setup cr

Re: Exclude cygwin folder from malware scans?

While it's true that not many viruses will target Cygwin directly, there are some that target folders based on string matching. For instance, a few years ago my computer at work caught a virus which apparently tried to spread itself through peer-to-peer file-sharing. It looked for folders with th

Re: Weird cosmetic bug after viewing bash man page

On 12/15/06, Buchbinder, Barry (NIH/NIAID) [E] wrote: Aaron Humphrey wrote on Friday, December 15, 2006 5:34 PM: > Oddly enough, it seems to. In fact, just adding the '-c' option to > NROFF in man.conf, without having to remove '-Tlatin' or add the '2> >

Re: Weird cosmetic bug after viewing bash man page

On 12/15/06, Buchbinder, Barry (NIH/NIAID) [E] wrote: I'm wondering whether this might be related to this old problem. http://sources.redhat.com/ml/cygwin/2006-11/msg00734.html I was having man pages where bold was not turn off properly. If I remember correctly, this suggestion fixed it for me.

Re: Weird cosmetic bug after viewing bash man page

On 12/14/06, Matthew Woehlke wrote: Aaron Humphrey wrote: > It seems to vary. I see it with 'man vim' and 'man printf' after the > first screen, for instance, but not with 'man man', unless I pick just > the right line. Which makes it seem less likely

Re: Weird cosmetic bug after viewing bash man page

On 12/14/06, Matthew Woehlke wrote: Ok, this is useful; it sounds like 'man bash' is in fact leaving the bold attribute turned on incorrectly. Aaron, in your case your prompt does not clear the attribute; I assume "printf '\033[0m'" fixes things? It does indeed. Does this only happen with the

Re: Weird cosmetic bug after viewing bash man page

I've seen this as well, my prompt(and everything I type)turning white if I don't go through the "bash" man page all the way to the end. I note that "stty sane" does nothing, nor does hitting enter; my prompt stays white. (This is in tcsh, where my "prompt" variable is "[EMAIL PROTECTED] %c02]$".

Re: cygwin.bat improvements (was Re: Cygwin on XP disapearing terminal mystery)

On 1/31/06, Brian Dessent wrote: > Well that would certainly work for the case of a missing bash. I guess > I was thinking that the marker file method would work for a wider range > of brokenness where for whatever reason the shell fails to start and/or > complete its initialization. Having never

Re: cygstart regression [Was: Re: on the road to 1.5.19 - snapshot testing needed]

On 10/2/05, Michael Schaap wrote: > To be able to check whether something has changed in the path handling, > I've uploaded a version of cygstart that prints out the exact > ShellExecute call it is making, at > . Could you perhaps download > that, try it out

Re: on the road to 1.5.19 - snapshot testing needed

I just did some version testing on the cygstart .mdb problem I reported a few days ago(http://cygwin.com/ml/cygwin/2005-09/msg00923.html), and it is indeed a regression from 1.5.18. Cygstart works fine with 1.5.18, but as early as the 20050909 snapshot(as far back as I have)it fails on MDB files.

Re: Funny hang with snapshop 20050920

On 9/23/05, Christopher Faylor wrote: > Also could anyone who could duplicate the Windows 98 error popup dialog > confirm or deny if it is still fixed? I was unable to produce the error using scp with the 20050925 snapshot(the whole cygwin-inst, in fact). So far, so good. -- --Alfvaen(Web page:

Re: testers needed prior to 1.5.19 release

On 9/14/05, Christopher Faylor wrote: > This will be fixed in the upcoming snapshot. Look for the comment: > * spawn.cc (av::fixup): Guard against problems reading an executable > which does not match Microsoft's documentation about PE format. > in the ChangeLog. Once that shows

Re: testers needed prior to 1.5.19 release

The Win98 scp problem seems to be gone with the 20050913 snapshot. It was always intermittent, but I copied several files last night and found no crashes, so it seems to be fixed. -- --Alfvaen (Web page: http://www.telusplanet.net/public/alfvaen/ ) Current Album--Sheryl Crow:C'mon C'mon Current

Re: Intermittent scp crash on completion, Win98 SE, snapshot

Unfortunately, using strace -p on the running scp process, with the latest snapshot, just brings up an unkillable "invalid page fault in KERNEL32.DLL" dialog. I now officially have no clue how to track this problem down. (Well, okay, in theory I could compile myself debugging versions of all appr

Re: Intermittent scp crash on completion, Win98 SE, snapshot

On 9/6/05, Aaron Humphrey wrote: > I tried a few times on the weekend, but no success yet. The first time, > strace crashed right away, leaving me with an unkillable error window, > which left me gunshy for a couple of days. When I tried it again this > morning, it did much th

Re: Intermittent scp crash on completion, Win98 SE, snapshot

On 9/2/05, Christopher Faylor wrote: > On Fri, Sep 02, 2005 at 07:27:46PM -0600, Aaron Humphrey wrote: > If you can get this to fail under strace, that would probably point to > the problem pretty quickly. It looks like something is trying to get > the pid of the process during the

Re: Bash/strtoimax error on setup

> Bash-3.0-8 requires cygwin-1.5.18 or newer, in order to satisfy the > strtoimax entry point. But according to your cygcheck output, you > now have that version: > > Cygwin DLL version info: > > DLL version: 1.5.18 > > > bash3.0-8 > My guess is that you were upg

Re: Cygwin 1.5.13 Vs. SETI@Home on Windows XP

On Thu, 17 Mar 2005 18:30:03 -0800, David Rothenberger wrote: > On 3/17/2005 6:20 PM, John Whitlock wrote: > > I was having the same problem as Patrick Graebal (see Bash hangs, CTRL-C > > required). The cygwin shell was very slow to start, and executing > > "bash --login -i -x" showed that the tim

Re: Obscene content in cygwin file.

>>> [EMAIL PROTECTED] 01/05/05 09:38PM >>> > Maybe we need a vote. I would really like to know how people feel about > this. We haven't had a vote in a long time so: > How do you feel about the off-color content in the cygwin fortune files? [ ] Offended. Think about the children! [ ] Not

Re: Setup column far too wide

On Tue, 9 Nov 2004, Christopher Faylor wrote: >> The column width is as long as the widest version number. It seems fine >> to me. It's certainly not 3/4 of the screen width on my system. Igor Pechtchanski wrote: >There was a package at some point that confused setup's versioning logic, >so set

Setup column far too wide

Where does Setup store its column widths, if any? I'm using Setup version 2.427, and on every view the "Current" column is far, far too wide. At 1280x1024 resolution, it's at least 3/4 of the screen width. It's been doing this for a few weeks, at least, and I have to manually resize the colum

Re: bash closes immediatly (other shells too)

>>> "Henrik Badekow" writes >>> > I just installed cygwin on my computer. I have been using it on other > computers since quite a while ago. This time I cant start it after the > installation. It just closes after about 2 seconds. This fact cannot be due > to a problem with the bash, cause it hap

Re: Cygwin shells exit immediately

Igor Pechtchanski wrote: > Did you try running bash non-interactively with a long-running command, > e.g., 'bash -c "sleep 20"'? Does that work? It doesn't return an error, but it doesn't take any more or less time to return than bash -c "sleep 1" or bash -c "sleep 150" > Does 'bash --norc -i

Re: Cygwin shells exit immediately

Further (mostly negative) information on the problem: Nothing shows up in the Windows System Log when bash exits. Bash stays open to type maybe half a dozen characters, and can run, say, "ls" before exiting. A reboot didn't help. Another person on the same network has no problems with Cygwin,

Fltk install hangs

I am also experiencing a hang installing fltk. (I would reply to http://cygwin.com/ml/cygwin/2003-11/msg00187.html, but at work I'm only subscribed to the digest list, and it hasn't shown up yet.) I was just doing a routine update of all packages, using the ftp.plig.net mirror(selected more or

RE: complete.tcsh doesn't handle spaces in $HOME

>>> "Hannu E K Nevalainen (garbage mail)" <[EMAIL PROTECTED]> 04/02/03 11:35AM >>> >>> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf >> Of Aaron Humphrey >> An easy workaround for this problem is just to wrap all of the >

complete.tcsh doesn't handle spaces in $HOME

I have been using Cygwin on a Windows 2000 computer running on a Novell network; my local user name is "Aaron Humphrey", and so my home directory is "/home/Aaron Humphrey". I've been trying to use tcsh, but it would abort out of the startup scripts, saying "If: