From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <pedro@palves.net>
Cc: gdb@sourceware.org
Subject: Re: GDB BoF notes - GNU Cauldron 2023
Date: Thu, 28 Sep 2023 14:44:47 -0600 [thread overview]
Message-ID: <87zg1610zk.fsf@tromey.com> (raw)
In-Reply-To: <1e26c71e-e242-de11-a687-46e05586e608@palves.net> (Pedro Alves's message of "Wed, 27 Sep 2023 13:41:47 +0100")
>>>>> "Pedro" == Pedro Alves <pedro@palves.net> writes:
Pedro> - Revisiting defaults
Pedro> - Can we turn history saving on by default? Maybe default to
Pedro> history on home dir by default, too (~/.gdb_history). That would
Pedro> align us with bash.
Maybe some XDG directory?
Anyway +1 for this from me.
Pedro> - Can we disable pagination by default? Surprisingly, no one in the
Pedro> room expressed that they like pagination on.
I leave it on but I can't say I really like it. Mostly I suppose it's a
distraction and I just haven't bothered changing it.
Pedro> "(gdb) pipe GDB_COMMAND | less"
I wonder if "with pagination on" works too.
Anyway +1 on this too.
Some other defaults to consider:
set print object on
set breakpoint pending on
set print pretty on
The last one is iffy I guess, maybe people like the compact output. The
first two I think I've had to tell many people about over the years.
Tom
next prev parent reply other threads:[~2023-09-28 20:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 12:41 Pedro Alves
2023-09-27 13:55 ` Simon Marchi
2023-09-27 14:00 ` Guinevere Larsen
2023-09-29 9:24 ` Lancelot SIX
2023-09-29 9:52 ` Turn history saving on by default? (Re: GDB BoF notes - GNU Cauldron 2023) Pedro Alves
2023-09-29 10:30 ` Guinevere Larsen
2023-09-27 20:27 ` GDB BoF notes - GNU Cauldron 2023 John Baldwin
2023-09-29 9:57 ` Pedro Alves
2023-10-06 21:35 ` John Baldwin
2023-09-28 20:44 ` Tom Tromey [this message]
2023-09-29 4:48 ` Sam James
2023-09-29 10:25 ` Pedro Alves
2023-10-05 7:08 ` Tom de Vries
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=87zg1610zk.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb@sourceware.org \
--cc=pedro@palves.net \
/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).