From: Eli Zaretskii <eliz@gnu.org>
To: Chet Ramey <chet.ramey@case.edu>,
Andrew STUBBS <andrew.stubbs@st.com>,
Denis PILAT <denis.pilat@st.com>,
gdb-patches@sources.redhat.com, bash-maintainers@gnu.org
Cc: chet.ramey@case.edu
Subject: Re: [readline-mingw] backspace key and TUI size
Date: Wed, 08 Feb 2006 17:54:00 -0000 [thread overview]
Message-ID: <ur76d4tzb.fsf@gnu.org> (raw)
In-Reply-To: <20060208171323.GA30534@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 8 Feb 2006 12:13:23 -0500)
> Date: Wed, 8 Feb 2006 12:13:23 -0500
> From: Daniel Jacobowitz <drow@false.org>
> Cc: Andrew STUBBS <andrew.stubbs@st.com>, Denis PILAT <denis.pilat@st.com>, 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.
next prev parent reply other threads:[~2006-02-08 17:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-08 8:03 Denis PILAT
2006-02-08 13:43 ` Daniel Jacobowitz
2006-02-08 16:03 ` Denis PILAT
2006-02-08 16:05 ` Bob Rossi
2006-02-08 16:14 ` Daniel Jacobowitz
2006-02-08 16:30 ` Chet Ramey
2006-02-08 16:48 ` Andrew STUBBS
2006-02-08 16:51 ` Daniel Jacobowitz
2006-02-08 17:04 ` Chet Ramey
2006-02-08 17:13 ` Daniel Jacobowitz
2006-02-08 17:54 ` Eli Zaretskii [this message]
2006-02-08 17:09 ` Eli Zaretskii
2006-02-08 17:30 ` Andrew STUBBS
2006-02-08 17:40 ` Daniel Jacobowitz
2006-02-09 9:36 ` Denis PILAT
2006-02-09 13:49 ` Daniel Jacobowitz
2006-02-10 15:41 ` Denis PILAT
2006-02-10 18:52 ` Eli Zaretskii
2006-02-20 15:36 ` Daniel Jacobowitz
2006-02-23 18:25 ` Daniel Jacobowitz
2006-02-24 8:36 ` Eli Zaretskii
2006-02-24 18:44 ` Daniel Jacobowitz
2006-02-24 18:48 ` Eli Zaretskii
2006-02-24 19:29 ` Daniel Jacobowitz
2006-02-25 11:35 ` Eli Zaretskii
2006-02-08 17:56 ` Eli Zaretskii
2006-02-08 18:03 ` Daniel Jacobowitz
2006-02-08 16:28 ` Eli Zaretskii
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=ur76d4tzb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=andrew.stubbs@st.com \
--cc=bash-maintainers@gnu.org \
--cc=chet.ramey@case.edu \
--cc=denis.pilat@st.com \
--cc=gdb-patches@sources.redhat.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