public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Igor Peshansky <pechtcha@cs.nyu.edu>
To: The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>,
	        The Cygwin-Talk Maiming List <cygwin-talk@cygwin.com>
Subject: RE: cygwin + windows update = lock up (W2K SP4)
Date: Sat, 20 May 2006 01:35:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.63.0605192134490.16587@access1.cims.nyu.edu> (raw)
In-Reply-To: <Pine.GSO.4.63.0605192128420.16587@access1.cims.nyu.edu>

On Fri, 19 May 2006, Igor Peshansky wrote:

> On Fri, 19 May 2006, Dave Korn wrote:
>
> > On 19 May 2006 16:27, Christopher Faylor wrote:
> >
> > > Anway, yes, I believe that the problem is fixed in the latest snapshot.
> >
> >   I certainly can't reproduce it any more.
> >
> >   Oh, hang on, I did just upgrade my ProcExp to the latest version.
> > <double-checks with old version>  Nope, it's really gone!
>
> Incidentally, this also (partly) fixed another pretty annoying problem I
> had with yesterday's CVS build: starting an xterm via a Windows
> (Hummingbird) inetd service popped up a DOS console titled
> "c:\cygwin\bin\xterm.exe".  That console doesn't pop up anymore (all I did
> was pick up CGF's patch to dtable.cc and rebuild from CVS).  However,
                             ^^^^^^^^^
Whoops!  Make that fhandler_console.cc.  This isn't called the mindless
chatter list for nothing, I guess.

> starting an xterm with a shortcut or cygstart still results in an extra
> console window.  I should probably report it properly on the main list --
> feel free to drop a hippo on me.

Hippos away!
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

  reply	other threads:[~2006-05-20  1:35 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-19 12:03 John Hackett
2006-05-19 12:13 ` Danilo Turina
2006-05-19 12:15 ` Dave Korn
2006-05-19 12:30   ` John Hackett
2006-05-19 12:44     ` Dave Korn
2006-05-19 15:12     ` mwoehlke
2006-05-19 15:18       ` Dave Korn
2006-05-19 15:25         ` mwoehlke
2006-05-19 23:22         ` Gary R. Van Sickle
2006-05-22 12:27           ` Dave Korn
2006-05-19 15:26     ` Christopher Faylor
2006-05-19 15:46       ` Dave Korn
2006-05-20  1:01         ` Igor Peshansky
2006-05-20  1:03           ` Christopher Faylor
2006-05-20  1:14             ` Igor Peshansky
2006-05-20  1:34         ` Igor Peshansky
2006-05-20  1:35           ` Igor Peshansky [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-03  9:12 Ludovic Drolez
2006-05-03 15:59 ` Christopher Faylor
2006-05-03 17:30   ` Dave Korn
2006-05-03 17:46     ` Christopher Faylor
2006-05-03 18:14       ` Dave Korn
2006-05-13 22:49       ` Christopher Faylor
     [not found] <003e01c66e19$caab4ea0$a501a8c0@CAM.ARTIMI.COM>
     [not found] ` <4457C0DB.F0093A96@dessent.net>
2006-05-02 20:59   ` Shankar Unni
2006-05-02 21:10     ` Christopher Faylor
2006-05-03 10:38       ` Dave Korn
2006-05-03 12:21         ` Igor Peshansky
2006-05-03 12:33           ` Gary R. Van Sickle
2006-05-03 13:43             ` Dave Korn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.GSO.4.63.0605192134490.16587@access1.cims.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin-talk@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).