From: Pedro Alves <pedro@palves.net>
To: Aleksey Midenkov <midenok@gmail.com>, gdb@sourceware.org
Subject: Re: set width: how to restore to auto
Date: Wed, 23 Aug 2023 13:14:19 +0100 [thread overview]
Message-ID: <dd4cf36e-3eb8-154f-bf5c-bb59cd20690c@palves.net> (raw)
In-Reply-To: <CAF8BazDRc5qrjo34JZh6POW5B-4dMB2hO4bsnvaHkL87FRrVXQ@mail.gmail.com>
On 23/08/23 10:53, Aleksey Midenkov via Gdb wrote:
> To avoid line wrapping in backtrace we use:
>
> set width 0
>
> How to restore it to auto without resizing the terminal?
I guess having "set width/height auto" would make sense.
> Why after resizing the terminal defined width is lost?
Indeed, "auto" could fix this, by making anything non-auto stick.
I suggest filing a bug report about this.
>
> Looks like there is not enough control over this parameter to implement two
> backtrace macros with and without line wrapping.
>
If it's just the one command you want to wrap, you can do:
(gdb) alias bt0 = with width 0 -- backtrace
(gdb) bt0 [ARG...]
...
prev parent reply other threads:[~2023-08-23 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 9:53 Aleksey Midenkov
2023-08-23 12:14 ` Pedro Alves [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=dd4cf36e-3eb8-154f-bf5c-bb59cd20690c@palves.net \
--to=pedro@palves.net \
--cc=gdb@sourceware.org \
--cc=midenok@gmail.com \
/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).