From: Balazs Kezes <rlblaster@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Correct origin calculation of command line window in TUI mode
Date: Wed, 28 Jul 2010 07:24:00 -0000 [thread overview]
Message-ID: <AANLkTikcWBtWH3ukhH0v5JekXRmVNvUfu82bCtTmgxhu@mail.gmail.com> (raw)
In-Reply-To: <201007272346.46299.pedro@codesourcery.com>
> These three patches now put you at borderline of
> what we can accept without copyright assignment to the FSF. Do
> you have that taken care of? If not, let us know, and we'll start
> you on the process.
I'm not sure what you are talking about. I don't think I'll be doing a lot
more work on this so it might be superfluous if this means what I think.
On 7/28/10, Pedro Alves <pedro@codesourcery.com> wrote:
> On Tuesday 27 July 2010 23:38:02, Balazs Kezes wrote:
>> > Hmmm, I've tried all three patches together, and I still get a messed
>> > up cmd window after a couple of resizes (e.g., start
>> > maxized/unmaximize/maximize).
>>
>> Yeah, these 3 patches are not enough. There are two remaining
>> modifications
>> which need to be done:
>
> Ah.
>
>> 1) HAVE_RESIZE_TERM - to make sure ncurses knows about the terminal size.
>> Somehow this needs to be added to the configuration. I'm not sure how
>> to do
>> this. Maybe I'll look into this sometime.
>
> I'll do this. These three patches now put you at borderline of
> what we can accept without copyright assignment to the FSF. Do
> you have that taken care of? If not, let us know, and we'll start
> you on the process.
>
>> 2) The readline modification in order to have correct sizes. I've already
>> contacted the readline guys and they told me that this bug will be
>> fixed in
>> readline 6.2.
>
> That's good news. In that case, I don't think there's a problem in
> backporting the fix to our local copy. Distros can do the same to
> their system readline's if they care too.
>
>> Even after this there is a little annoyance that you need to press a
>> key to actually resize and redraw everything, but this could be fixed
>> by ungetc or with a similar hack.
>>
>> Here are the changelogs:
>
> Thanks. I'll take another look at this soon.
>
> --
> Pedro Alves
>
next prev parent reply other threads:[~2010-07-28 7:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-21 21:02 Balazs Kezes
2010-07-27 14:43 ` Pedro Alves
2010-07-27 22:38 ` Balazs Kezes
2010-07-27 22:46 ` Pedro Alves
2010-07-28 7:24 ` Balazs Kezes [this message]
2010-07-28 9:59 ` Pedro Alves
2010-07-28 11:50 ` Pedro Alves
2010-07-28 12:03 ` Pedro Alves
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=AANLkTikcWBtWH3ukhH0v5JekXRmVNvUfu82bCtTmgxhu@mail.gmail.com \
--to=rlblaster@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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