From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11074 invoked by alias); 8 Feb 2006 17:54:16 -0000 Received: (qmail 11057 invoked by uid 22791); 8 Feb 2006 17:54:14 -0000 X-Spam-Check-By: sourceware.org Received: from romy.inter.net.il (HELO romy.inter.net.il) (192.114.186.66) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 08 Feb 2006 17:54:14 +0000 Received: from HOME-C4E4A596F7 (IGLD-80-230-155-31.inter.net.il [80.230.155.31]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id DNK03688 (AUTH halo1); Wed, 8 Feb 2006 19:53:59 +0200 (IST) Date: Wed, 08 Feb 2006 17:54:00 -0000 Message-Id: From: Eli Zaretskii To: Chet Ramey , Andrew STUBBS , Denis PILAT , gdb-patches@sources.redhat.com, bash-maintainers@gnu.org CC: chet.ramey@case.edu In-reply-to: <20060208171323.GA30534@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 8 Feb 2006 12:13:23 -0500) Subject: Re: [readline-mingw] backspace key and TUI size Reply-to: Eli Zaretskii References: <43E9A5B1.1030001@st.com> <20060208134335.GA22980@nevyn.them.org> <43EA1655.609@st.com> <20060208161452.GA26965@nevyn.them.org> <43EA201B.5080305@st.com> <20060208165114.GA28698@nevyn.them.org> <43EA2464.8040306@case.edu> <20060208171323.GA30534@nevyn.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-02/txt/msg00182.txt.bz2 > Date: Wed, 8 Feb 2006 12:13:23 -0500 > From: Daniel Jacobowitz > Cc: Andrew STUBBS , Denis PILAT , gdb-patches@sources.redhat.com, bash-maintainers@gnu.org, chet@case.edu > > On Wed, Feb 08, 2006 at 12:03:32PM -0500, Chet Ramey wrote: > > Daniel Jacobowitz wrote: > > > > > Please, guys, if you're going to submit patches that only matter with > > > other configuration changes and patches, say so! > > > > > > I'd like to understand what goes wrong for you and why outputing > > > whatever pdcurses is giving you for backspace doesn't work. > > > > Can we all agree that the screensize code is valuable, at least? > > Absolutely! Eli pointed out that it needs some error checking; this > is somewhat important, because stdin might not be connected to a > console (e.g. a pipe). But other than that it looked right to me. Yes, apart of the bit with error checking, the MinGW screen-size code is okay with me.