Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew STUBBS <andrew.stubbs@st.com>
To: Jon Ringle <JRingle@vertical.com>,
	chet.ramey@case.edu, 	andrew.stubbs@st.com, eliz@gnu.org,
	denis.pilat@st.com, 	gdb-patches@sources.redhat.com,
	bash-maintainers@gnu.org
Subject: Re: pdcurses readline-mingw backspace key in windows console
Date: Mon, 28 Jul 2008 12:48:00 -0000	[thread overview]
Message-ID: <488DBFB1.2070008@st.com> (raw)
In-Reply-To: <20080719211038.GA4920@caradoc.them.org>

Daniel Jacobowitz wrote:
> On Sat, Jul 19, 2008 at 04:08:46PM -0400, Jon Ringle wrote:
>> Chet Ramey wrote:
>>> And if I read the pdcurses maintainer's reply correctly, the response
>> is
>>> "if you want terminfo, look somewhere else."  Readline is not going to
>>> become a curses-based application, so it appears that using pdcurses
>>> with readline is a dead end.
>> What would you recommend then for a mingw readline-based application
>> that is run from a Windows console?

>> I suppose I could just provide my own terminfo stubs and link with that
>> to satisfy readline... The only reason that I was trying to link in a
>> curses library was to satisfy readline terminfo dependencies.

> GDB and its included readline should already build on mingw32 without
> a curses library.  Make sure you're using a current version.

GDB does build without curses, but the GDB TUI won't work without.

Sorry for the delayed response, it's taken a while to check.

Andrew


      reply	other threads:[~2008-07-28 12:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4DD3AF7ECBBC43409BA36508938D01852CF053@CVAEX1.VERTICAL.COM>
2008-07-19 15:48 ` Chet Ramey
2008-07-19 20:09   ` Jon Ringle
2008-07-19 21:11     ` Daniel Jacobowitz
2008-07-28 12:48       ` Andrew STUBBS [this message]

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=488DBFB1.2070008@st.com \
    --to=andrew.stubbs@st.com \
    --cc=JRingle@vertical.com \
    --cc=bash-maintainers@gnu.org \
    --cc=chet.ramey@case.edu \
    --cc=denis.pilat@st.com \
    --cc=eliz@gnu.org \
    --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