public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "aburgess at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tui/30502] [gdb/tui] output window Date: Thu, 01 Jun 2023 09:43:08 +0000 [thread overview] Message-ID: <bug-30502-4717-dC6CzjZIzI@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30502-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30502 Andrew Burgess <aburgess at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |aburgess at redhat dot com --- Comment #1 from Andrew Burgess <aburgess at redhat dot com> --- Adding this link just so there's a record. Pedro made a start on having the inferior always write into a pseudo tty in this series: https://inbox.sourceware.org/gdb-patches/20210614212410.1612666-1-pedro@palves.net/ This doesn't try to address the TUI overwrite problem, but in theory should be the basis for allowing GDB to keep the inferior output and TUI prompts in the same window while avoiding the overwrite issue. That said having the option of a separate output window would be a nice choice, but I think it should be a choice. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2023-06-01 9:43 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-31 23:35 [Bug tui/30502] New: " vries at gcc dot gnu.org 2023-06-01 9:43 ` aburgess at redhat dot com [this message]
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=bug-30502-4717-dC6CzjZIzI@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).