public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/30388] [gdb/tui, TERM=ansi] first char of prompt in status line
Date: Tue, 25 Apr 2023 11:30:04 +0000	[thread overview]
Message-ID: <bug-30388-4717-Rpqfeij2DO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30388-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=30388

--- Comment #5 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> This seems to help in some cases, but not all:
> ...
> -  waddstr (handle.get (), string.c_str ());
> +  waddnstr (handle.get (), string.c_str (), width - 1);
> ...

This case is fine:
...
$ TERM=ansi gdb -q -eiex "set tui border-kind ascii" -tui 
...
but this case still has the same problem:
...
$ TERM=ansi gdb -q -iex "set tui border-kind ascii" -tui
...

Also works fine with:
...
$ TERM=ansi gdb -q -iex "set tui border-kind ascii" -iex "tui enable"
...
and:
...
$ TERM=ansi gdb -q -eiex "set tui border-kind ascii" -iex "tui enable"
...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-04-25 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25  9:45 [Bug tui/30388] New: " vries at gcc dot gnu.org
2023-04-25 10:08 ` [Bug tui/30388] " vries at gcc dot gnu.org
2023-04-25 10:19 ` vries at gcc dot gnu.org
2023-04-25 10:52 ` vries at gcc dot gnu.org
2023-04-25 10:53 ` vries at gcc dot gnu.org
2023-04-25 11:30 ` vries at gcc dot gnu.org [this message]
2023-04-25 13:07 ` vries at gcc dot gnu.org
2023-05-04  7:37 ` vries at gcc dot gnu.org
2023-05-09 13:22 ` 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-30388-4717-Rpqfeij2DO@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: 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).