public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "blarsen at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/31033] New: Bogus bold at the end of command when quitting pagination early Date: Mon, 06 Nov 2023 11:33:17 +0000 [thread overview] Message-ID: <bug-31033-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31033 Bug ID: 31033 Summary: Bogus bold at the end of command when quitting pagination early Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: gdb Assignee: unassigned at sourceware dot org Reporter: blarsen at redhat dot com Target Milestone: --- When a command has bold in its output, triggers pagination, and the user quits pagination early, the next command will have bold at the end and the prompt will be printed in bold as well. See this sample session, using <bold></bold> to show where the output is stylized: $ ./gdb -q cat Reading symbols from cat... Reading symbols from .gnu_debugdata for /usr/bin/cat... (No debugging symbols found in .gnu_debugdata for /usr/bin/cat) (gdb) set height 2 (gdb) apropos inferior <bold> add-inferior </bold> -- Add a new inferior. --Type <RET> for more, q to quit, c to continue without paging--q Quit (gdb) inferior [Current inferior is 1 <bold>[<null>] (/usr/bin/cat)] (gdb)</bold> inferior [Current inferior is 1 [<null>] (/usr/bin/cat)] (gdb) This is a regression, since this behavior isn't present in GDB 13.2-3 in Fedora 37. -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2023-11-06 11:33 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-31033-4717@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).