Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Chet Ramey <chet.ramey@case.edu>
To: Jon Ringle <JRingle@vertical.com>
Cc: andrew.stubbs@st.com, drow@false.org, eliz@gnu.org,
	denis.pilat@st.com,         gdb-patches@sources.redhat.com,
	bash-maintainers@gnu.org,         chet.ramey@case.edu
Subject: Re: pdcurses readline-mingw backspace key in windows console
Date: Sat, 19 Jul 2008 15:48:00 -0000	[thread overview]
Message-ID: <48820CB0.9000502@case.edu> (raw)
In-Reply-To: <4DD3AF7ECBBC43409BA36508938D01852CF053@CVAEX1.VERTICAL.COM>

Jon Ringle wrote:
> Folks,
> 
>  
> 
> I ran into the same problem regarding the backspace key with 
> pdcurses/readline/mingw in a windows console  that was discussed a 
> couple years ago here 
> http://www.cygwin.com/ml/gdb-patches/2006-02/msg00180.html.
> 
>  
> 
> This problem still exists today with pdcurses-3.3 and I believe that I 
> have found the problem and have submitted a patch to the pdcurses 
> project here:
> 
>  
> 
> http://sourceforge.net/tracker/index.php?func=detail&aid=2021778&group_id=30480&atid=399168 
> <http://sourceforge.net/tracker/index.php?func=detail&aid=2021778&group_id=30480&atid=399168>

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.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/


       reply	other threads:[~2008-07-19 15: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 [this message]
2008-07-19 20:09   ` Jon Ringle
2008-07-19 21:11     ` Daniel Jacobowitz
2008-07-28 12:48       ` Andrew STUBBS

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=48820CB0.9000502@case.edu \
    --to=chet.ramey@case.edu \
    --cc=JRingle@vertical.com \
    --cc=andrew.stubbs@st.com \
    --cc=bash-maintainers@gnu.org \
    --cc=denis.pilat@st.com \
    --cc=drow@false.org \
    --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