Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Denis PILAT <denis.pilat@st.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com, bash-maintainers@gnu.org
Subject: Re: [readline-mingw] backspace key and TUI size
Date: Wed, 08 Feb 2006 16:03:00 -0000	[thread overview]
Message-ID: <43EA1655.609@st.com> (raw)
In-Reply-To: <20060208134335.GA22980@nevyn.them.org>

Daniel Jacobowitz wrote:

>On Wed, Feb 08, 2006 at 09:02:57AM +0100, Denis PILAT wrote:
>  
>
>>Hi,
>>
>>When compiling gdb 6.4 for native window host (minGW) I get a gdb.exe 
>>and a gdbtui.exe where there were 2 problems.
>>- In the gdbtui.exe version, the TUI interface do not fit in the DOS 
>>command window.
>>- In the gdb.exe version, the backspace key do not behave correctly.
>>
>>I did some little modification in readline to fix both problems. I 
>>attach the patch applied.
>>I've already submitted it to Chet Ramey (the readline maintainer at 
>>bash-maintainers@gnu.org) who accepted it.
>>I don't know the gdb policy with readline synchronization, but I would 
>>like it  to be integrated as well in gdb distribution.
>>    
>>
>
>We can import readline patches; I assume Chet didn't take this as-is
>(it has a stray printf in it).  Chet, if you have a chance, could you
>send us the version you've applied, so we can merge it?
>
>Denis, I'm not sure why the backspace fix was necessary for you; my
>backspace works fine.  What did this fix?
>
>  
>
You're right, I forgot to remove a printf ...

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.

Denis




  reply	other threads:[~2006-02-08 16: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 [this message]
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
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=43EA1655.609@st.com \
    --to=denis.pilat@st.com \
    --cc=bash-maintainers@gnu.org \
    --cc=drow@false.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