From: Daniel Jacobowitz <drow@false.org>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Denis PILAT <denis.pilat@st.com>,
gdb-patches@sources.redhat.com, bash-maintainers@gnu.org
Subject: Re: [readline-mingw] backspace key and TUI size
Date: Wed, 08 Feb 2006 17:40:00 -0000 [thread overview]
Message-ID: <20060208173951.GA31572@nevyn.them.org> (raw)
In-Reply-To: <43EA2A39.4000107@st.com>
On Wed, Feb 08, 2006 at 05:28:25PM +0000, Andrew STUBBS wrote:
> Eli Zaretskii wrote:
> >>Date: Wed, 8 Feb 2006 11:51:14 -0500
> >>From: Daniel Jacobowitz <drow@false.org>
> >>Cc: Denis PILAT <denis.pilat@st.com>, gdb-patches@sources.redhat.com,
> >>bash-maintainers@gnu.org
> >>
> >>I'd like to understand what goes wrong for you and why outputing
> >>whatever pdcurses is giving you for backspace doesn't work.
> >
> >Seconded. Please explain why Backspace doesn't work (if you don't
> >know, please debug this on your system and see what you come up with).
> >Thanks.
>
> It does work in MSYS terminals. In DOS/Windows or Cygwin terminals it
> moves the cursor right, instead of left, and leaves the deleted
> character on the screen. I assume that this curses just doesn't support
> those terminals in this respect.
Well that's why then.
The way a termcap library works is that it describes the capabilities
of each individual terminal that it supports; the control sequences it
outputs rely on knowing in advance how a particular terminal will
respond to various conditions.
If the mingw build of pdcurses works in an MSYS terminal and explodes
in a DOS console, then the MSYS terminal must implement something
different than the DOS console; if the curses library is not aware
of the difference, things will break. Please don't adjust readline
for this; instead get pdcurses not to report the capability or to
report it correctly.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-08 17:40 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
2006-02-08 17:09 ` Eli Zaretskii
2006-02-08 17:30 ` Andrew STUBBS
2006-02-08 17:40 ` Daniel Jacobowitz [this message]
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=20060208173951.GA31572@nevyn.them.org \
--to=drow@false.org \
--cc=andrew.stubbs@st.com \
--cc=bash-maintainers@gnu.org \
--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