From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17833 invoked by alias); 29 Jul 2008 18:00:14 -0000 Received: (qmail 17821 invoked by uid 22791); 29 Jul 2008 18:00:13 -0000 X-Spam-Check-By: sourceware.org Received: from pool-96-233-37-80.bstnma.fios.verizon.net (HELO ednor.cgf.cx) (96.233.37.80) by sourceware.org (qpsmtpd/0.31) with ESMTP; Tue, 29 Jul 2008 17:59:56 +0000 Received: by ednor.cgf.cx (Postfix, from userid 201) id C852C63305B; Tue, 29 Jul 2008 13:59:54 -0400 (EDT) Date: Tue, 29 Jul 2008 18:00:00 -0000 From: Christopher Faylor To: cygwin-apps@cygwin.com Subject: Re: base-[files|password] for 1.7 Message-ID: <20080729175954.GA11799@ednor.casa.cgf.cx> Reply-To: cygwin-apps@cygwin.com Mail-Followup-To: cygwin-apps@cygwin.com References: <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> <0f5cf79df02984f1e40c0b600041fbbd.squirrel@mail.morrison.mine.nu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0f5cf79df02984f1e40c0b600041fbbd.squirrel@mail.morrison.mine.nu> User-Agent: Mutt/1.5.16 (2007-06-09) 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/msg00179.txt.bz2 On Tue, Jul 29, 2008 at 05:18:32PM +0100, John Morrison wrote: >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? Adding the kill -WINCH still makes sense. It will at least get things working for xterm and rxvt. cgf