From: Eli Zaretskii <eliz@gnu.org>
To: Hannes Domani <ssbssa@yahoo.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCHv2 2/2] Add optional full_window argument to TuiWindow.write
Date: Fri, 21 May 2021 17:35:51 +0300 [thread overview]
Message-ID: <83fsygm9x4.fsf@gnu.org> (raw)
In-Reply-To: <20210521143322.1293-2-ssbssa@yahoo.de> (message from Hannes Domani via Gdb-patches on Fri, 21 May 2021 16:33:22 +0200)
> Date: Fri, 21 May 2021 16:33:22 +0200
> From: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
>
> To prevent flickering when first calling erase, then write, this new
> argument indicates that the passed string contains the full contents of
> the window. This fills every unused cell of the window with a space, so
> it's not necessary to call erase beforehand.
>
> gdb/ChangeLog:
>
> 2021-05-21 Hannes Domani <ssbssa@yahoo.de>
>
> * python/py-tui.c (tui_py_window::output): Add full_window
> argument.
> (gdbpy_tui_write): Parse "full_window" argument.
>
> gdb/doc/ChangeLog:
>
> 2021-05-21 Hannes Domani <ssbssa@yahoo.de>
>
> * python.texi (TUI Windows In Python): Document "full_window"
> argument.
OK for the documentation change.
Thanks.
next prev parent reply other threads:[~2021-05-21 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210521143322.1293-1-ssbssa.ref@yahoo.de>
2021-05-21 14:33 ` [PATCHv2 1/2] Prevent flickering when redrawing the TUI python window Hannes Domani
2021-05-21 14:33 ` [PATCHv2 2/2] Add optional full_window argument to TuiWindow.write Hannes Domani
2021-05-21 14:35 ` Eli Zaretskii [this message]
2021-05-24 14:17 ` Tom Tromey
2021-05-24 14:18 ` Tom Tromey
2021-05-24 14:25 ` Hannes Domani
2021-05-27 18:22 ` Tom Tromey
2021-05-27 18:44 ` Hannes Domani
2021-05-24 14:12 ` [PATCHv2 1/2] Prevent flickering when redrawing the TUI python window Tom Tromey
2021-05-24 15:18 ` Hannes Domani
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=83fsygm9x4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ssbssa@yahoo.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).