From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22565 invoked by alias); 29 Jul 2008 16:18:58 -0000 Received: (qmail 22553 invoked by uid 22791); 29 Jul 2008 16:18:57 -0000 X-Spam-Check-By: sourceware.org Received: from mtaout03-winn.ispmail.ntl.com (HELO mtaout03-winn.ispmail.ntl.com) (81.103.221.49) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 29 Jul 2008 16:18:36 +0000 Received: from aamtaout01-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout03-winn.ispmail.ntl.com with ESMTP id <20080729161834.DKPN10791.mtaout03-winn.ispmail.ntl.com@aamtaout01-winn.ispmail.ntl.com> for ; Tue, 29 Jul 2008 17:18:34 +0100 Received: from gateway.morrison.mine.nu ([82.21.193.42]) by aamtaout01-winn.ispmail.ntl.com with ESMTP id <20080729161834.BBQE5827.aamtaout01-winn.ispmail.ntl.com@gateway.morrison.mine.nu> for ; Tue, 29 Jul 2008 17:18:34 +0100 Received: from localhost ([127.0.0.1] helo=mail.morrison.mine.nu ident=www-data) by gateway.morrison.mine.nu with esmtp (Exim 4.69 #1 (Debian)) id 1KNruC-0002j7-6c for ; Tue, 29 Jul 2008 17:18:32 +0100 Received: from 192.168.0.249 (SquirrelMail authenticated user john) by mail.morrison.mine.nu with HTTP; Tue, 29 Jul 2008 17:18:32 +0100 (BST) Message-ID: <0f5cf79df02984f1e40c0b600041fbbd.squirrel@mail.morrison.mine.nu> In-Reply-To: <20080729145754.GE29031@calimero.vinschen.de> References: <20080717155516.GC5675@calimero.vinschen.de> <20080719141841.GN5675@calimero.vinschen.de> <20080722174237.GA25430@calimero.vinschen.de> <5f21cb61c3a7cb7ad2d02df11907792e.squirrel@mail.morrison.mine.nu> <20080728152750.GN29031@calimero.vinschen.de> <488F00EB.8080606@byu.net> <9f5f2bd17addf8364a82964f81f06f94.squirrel@mail.morrison.mine.nu> <488F0697.6000202@byu.net> <20080729122919.GX29031@calimero.vinschen.de> <20080729143123.GE7379@ednor.casa.cgf.cx> <20080729145754.GE29031@calimero.vinschen.de> Date: Tue, 29 Jul 2008 16:18:00 -0000 Subject: Re: base-[files|password] for 1.7 From: "John Morrison" To: cygwin-apps@cygwin.com User-Agent: SquirrelMail/1.4.15 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit Mailing-List: contact cygwin-apps-help@cygwin.com; run by ezmlm Precedence: bulk Sender: cygwin-apps-owner@cygwin.com List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps@cygwin.com X-SW-Source: 2008-07/txt/msg00175.txt.bz2 On Tue, July 29, 2008 3:57 pm, Corinna Vinschen wrote: > On Jul 29 10:31, Christopher Faylor wrote: >> On Tue, Jul 29, 2008 at 02:29:19PM +0200, Corinna Vinschen wrote: >> >Chris, is there any good reason NOT to call send_winch_maybe on >> >a key event? >> >> It only makes sense when there is a mouse event. > > I don't understand that. Mouse events typically don't happen. I can > use the mouse as much as I want in a console window running vim, vim > never gets the SIGWINCH. > >> It would make more >> sense to move the handling of SIGWINCH into the signal handler so that >> the above works transparently. I'll look into doing that. > > That would be a nice addition. So I don't need to add anything to /etc/profile? J.