Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Simon Marchi <simark@simark.ca>,
	 tom@tromey.com,  midenok@gmail.com,  gdb-patches@sourceware.org
Subject: Re: GDB 9 TUI mode broken
Date: Sat, 22 Feb 2020 18:06:00 -0000	[thread overview]
Message-ID: <87tv3i5wee.fsf@tromey.com> (raw)
In-Reply-To: <83imjyip6n.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 22 Feb	2020 18:04:16 +0200")

>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:

Eli> The next question is: what code readjusts the location of the locator
Eli> window when the source or the command window is resized, and where is
Eli> that code called?  because the preceding code in
Eli> tui_adjust_win_heights modifies only 2 windows: the one whose height
Eli> was directly changed by the winheight command, and the other one,
Eli> which is displayed above or below it.

Other cases in tui_adjust_win_heights move the locator explicitly:

		  locator->resize (1, width,
				   0, (second_win->origin.y
				       + second_win->height + 1));

This just needs to be added to the first case, that you already
modified:

	  if (cur_layout == SRC_COMMAND 
	      || cur_layout == DISASSEM_COMMAND)
...

Tom


  parent reply	other threads:[~2020-02-22 18:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAF8BazBni=TZWTc5fbpdHU5bv1eM=24xpML46GCC2u4pFTkSAw@mail.gmail.com>
     [not found] ` <835zg5m7ib.fsf@gnu.org>
2020-02-22 11:33   ` Eli Zaretskii
2020-02-22 15:55     ` Simon Marchi
2020-02-22 16:04       ` Eli Zaretskii
2020-02-22 16:37         ` Eli Zaretskii
2020-02-22 18:06         ` Tom Tromey [this message]
2020-02-22 18:05     ` Tom Tromey
2020-02-22 18:23       ` Eli Zaretskii
2020-02-22 18:46         ` Eli Zaretskii
2020-02-22 19:10           ` Tom Tromey
2020-02-22 20:19             ` Eli Zaretskii
2020-02-22 19:02         ` Tom Tromey

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=87tv3i5wee.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=midenok@gmail.com \
    --cc=simark@simark.ca \
    /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