Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org, bash-maintainers@gnu.org
Subject: Re: [readline-mingw] backspace key and TUI size
Date: Wed, 08 Feb 2006 18:03:00 -0000	[thread overview]
Message-ID: <20060208180257.GA32320@nevyn.them.org> (raw)
In-Reply-To: <upslx4tvi.fsf@gnu.org>

On Wed, Feb 08, 2006 at 07:56:17PM +0200, Eli Zaretskii wrote:
> > Date: Wed, 8 Feb 2006 11:14:52 -0500
> > From: Daniel Jacobowitz <drow@false.org>
> > Cc: gdb-patches@sources.redhat.com, bash-maintainers@gnu.org
> > 
> > On Wed, Feb 08, 2006 at 05:03:33PM +0100, Denis PILAT wrote:
> > > Our host is i686-pc-mingw32, gdb is compiled under cygwin with 
> > > "-mno-cygwin" flag to avoid cygwin dependencies.
> > > We also use pdcurses library since ncurse is not available on windows.
> > > I think that's why you don't see the problem. With this patch, I'm not 
> > > using the tputs() function anymore on Windows, as it was not used for MSDOS.
> > 
> > Ah - we (CodeSourcery) don't use a curses library at all; just the
> > standard Windows and MinGW DLLs.  See win32-termcap.c.
> 
> But win32-termcap.c is not a general solution for readline, it's
> private to GDB, right?  SHouldn't this problem be solved in readline
> rather than in GDB (and in every other application that uses
> readline)?

I don't remember the reasoning, but this was discussed before, and
the current solution was preferred.  Either you give readline a termcap
library, or you supply stubs.  It sounds like there is a termcap
library we could make use of on Windows, but there isn't one
standard with the OS, and the one there is seems to have some
problems; I'm all for leaving alone one of the bits of this whole
mess which works OK...

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-02-08 18:03 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
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 [this message]
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=20060208180257.GA32320@nevyn.them.org \
    --to=drow@false.org \
    --cc=bash-maintainers@gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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