From: Andreas Schwab <schwab@suse.de>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb@sourceware.org
Subject: Re: Expected behaviour of 'set width XX'
Date: Thu, 20 Jul 2017 08:17:00 -0000 [thread overview]
Message-ID: <mvm60enzfoa.fsf@suse.de> (raw)
In-Reply-To: <20170720074853.GL27353@embecosm.com> (Andrew Burgess's message of "Thu, 20 Jul 2017 08:48:53 +0100")
On Jul 20 2017, Andrew Burgess <andrew.burgess@embecosm.com> wrote:
> So, my question: Is the current gdb behaviour the expected behaviour?
I think readline is relying on the terminal to actually have that width,
thus to wrap around without emitting a newline.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
prev parent reply other threads:[~2017-07-20 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 7:49 Andrew Burgess
2017-07-20 8:17 ` Andreas Schwab [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=mvm60enzfoa.fsf@suse.de \
--to=schwab@suse.de \
--cc=andrew.burgess@embecosm.com \
--cc=gdb@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