From: Tom Tromey <tom@tromey.com>
To: Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Cc: Tom Tromey <tom@tromey.com>, Tom de Vries <tdevries@suse.de>
Subject: Re: [PATCH] [gdb/tui] Handle unicode chars in prompt
Date: Fri, 09 Jun 2023 09:13:19 -0600 [thread overview]
Message-ID: <87ttvg7jow.fsf@tromey.com> (raw)
In-Reply-To: <26eace21-84bf-7d9d-051b-93f2bc38edd7@suse.de> (Tom de Vries via Gdb-patches's message of "Fri, 9 Jun 2023 00:44:39 +0200")
>>>>> "Tom" == Tom de Vries via Gdb-patches <gdb-patches@sourceware.org> writes:
Sorry, I missed this email when looking at your latest TUI patches.
Tom> The logic I used in this patch:
Tom> ...
Tom> + if (height != nullptr)
Tom> + {
Tom> + int line = getcury (w);
Tom> + *height += line - prev_line;
Tom> }
Tom> ...
Tom> was to use the current line to detect a wrap but that doesn't work if
Tom> writing the prompt wraps at the last line which then generates a
Tom> scroll.
Yeah, I see. This whole thing is maddening to me because ncurses does
have a flag that indicates that the output wrapped, and while it is in
curses.h, it is clearly non-exported, there's not even an ncurses
extension for it. And, PDcurses does not have this.
Tom> In conclusion, AFAIU this approach doesn't work.
Yeah :(
Tom
next prev parent reply other threads:[~2023-06-09 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 13:25 Tom de Vries
2023-05-26 13:56 ` Eli Zaretskii
2023-05-30 16:51 ` Tom Tromey
2023-06-09 9:34 ` Tom de Vries
2023-06-09 10:21 ` Eli Zaretskii
2023-05-26 15:44 ` Tom de Vries
2023-05-30 17:03 ` Tom Tromey
2023-05-30 18:07 ` DJ Delorie
2023-05-31 0:02 ` Tom Tromey
2023-05-31 11:29 ` Tom de Vries
2023-06-08 22:44 ` Tom de Vries
2023-06-09 15:13 ` Tom Tromey [this message]
2023-06-09 9:48 ` Tom de Vries
2023-06-09 15:15 ` Tom Tromey
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=87ttvg7jow.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.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).