public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug cli/30346] [gdb/cli] CLI in ansi terminal has off-by-one width problem Date: Fri, 05 May 2023 12:34:01 +0000 [thread overview] Message-ID: <bug-30346-4717-Xh3p8e8HSp@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30346-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30346 --- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom de Vries <vries@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=4891c459927d9a9c0f516c35e2d9d4ce212dd06e commit 4891c459927d9a9c0f516c35e2d9d4ce212dd06e Author: Tom de Vries <tdevries@suse.de> Date: Fri May 5 14:34:00 2023 +0200 [gdb/testsuite] Add gdb.base/wrap-line.exp Add a test-case that tests prompt edit wrapping in CLI, both for TERM=xterm and TERM=ansi, both with auto-detected and hard-coded width. In the TERM=ansi case with auto-detected width we run into PR cli/30346, so add a KFAIL for that failure mode. Tested on x86_64-linux. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-05-05 12:34 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-13 12:42 [Bug cli/30346] New: " vries at gcc dot gnu.org 2023-04-15 6:10 ` [Bug cli/30346] " vries at gcc dot gnu.org 2023-04-21 15:12 ` cvs-commit at gcc dot gnu.org 2023-05-05 12:34 ` cvs-commit at gcc dot gnu.org [this message] 2023-05-12 9:43 ` cvs-commit at gcc dot gnu.org 2023-05-12 9:46 ` vries at gcc dot gnu.org
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-30346-4717-Xh3p8e8HSp@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).