From: Guinevere Larsen via Gdb <gdb@sourceware.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: Improve GDB's first user experience by reducing "print_gdb_version" output
Date: Wed, 28 May 2025 09:15:59 -0300 [thread overview]
Message-ID: <7bf8f6cc-2017-4cd4-9b74-bddaa4f1a4d3@redhat.com> (raw)
In-Reply-To: <86plftvuaz.fsf@gnu.org>
On 5/28/25 8:39 AM, Eli Zaretskii wrote:
>> Date: Tue, 27 May 2025 17:43:18 -0300
>> From: Guinevere Larsen via Gdb<gdb@sourceware.org>
>>
>> GNU gdb (GDB) 17.0.50.20250526-git
>> Copyright (C) 2024 Free Software Foundation, Inc.
>> License GPLv3+: GNU GPL version 3 or later
>> <http://gnu.org/licenses/gpl.html>
>> This is free software: you are free to change and redistribute it.
>> There is NO WARRANTY, to the extent permitted by law.
>> Type "show copying" and "show warranty" for details.
>> This GDB was configured as "x86_64-pc-linux-gnu".
>> Type "show configuration" for configuration details.
>> For bug reporting instructions, please see:
>> <https://www.gnu.org/software/gdb/bugs/>.
>> Find the GDB manual and other documentation resources online at:
>> <http://www.gnu.org/software/gdb/documentation/>.
>>
>> For help, type "help".
>> Type "apropos word" to search for commands related to "word".
>> (gdb)
>>
>> For the *vast* majority of our users, only 4 of those lines are useful
>> at all: the GDB version (to ask for help), where to find the
>> documentation, the "help" command, and the "apropos" command. Arguably,
>> where to report bugs could be useful, but the worst ones already print
>> it and otherwise users are incredibly unlikely to report them
>> (especially given the email requirements to create an account). Worthy
>> of note, the important lines are the last ones, so even if a new user
>> was eager enough to start reading everything, they'd likely gloss over
>> everything assuming this entire thing is just copyright.
>>
>> I propose that the text be updated to something similar to this:
>>
>> GNU gdb (GDB) 17.0.50.20250526-git
>> For a list of commands, use "help"
>> For all commands related to a certain word, use "apropos word"
>> For a thorough explanation of what GDB can do, check the manual at:
>> <http://www.gnu.org/software/gdb/documentation/>
>> For information on GDB's copyright, warranty or configuration, use
>> "show copying/warranty/configuration"
>> (gdb)
> This line is NOT redundant, and conveys important information:
>
> This GDB was configured as "x86_64-pc-linux-gnu".
Strictly speaking, none of the lines in the introduction are fully
redundant, they will all be useful in niche situations. My claim is that
for most users, and especially new users, this reads as visual noise
that obscures the helpful commands to start using GDB. And worse in this
specific situation, I would expect that many cases where that knowledge
would be important, the information would have scrolled off the screen
and a refresher would be needed either way.
Further thinking about the end goal, it would be good to have an even
more descriptive message if GDB thinks that this can be an entirely new
user, which explains more things and would be disabled by adding
something to a gdbinit, something like "set existing-user 1", and
explaining what the gdbinit even is. With that, if a user ends up
finding that knowing the configuration is important, they will be aware
that they can add "show configuration".
> Also, why did you decide to change the wording of this line:
>
> Type "apropos word" to search for commands related to "word".
>
> I think the original wording was good.
>
The wording here isn't meant to be taken literally, it was chosen
quickly to illustrate what kind of changes I had in mind. The quick
change was just to standardize the suggestions as "for <intended
outcome>, use <command>", but that detail side of the discussion can be
left for when a patch making these changes
--
Cheers,
Guinevere Larsen
She/Her/Hers
prev parent reply other threads:[~2025-05-28 12:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 20:43 Guinevere Larsen via Gdb
2025-05-27 21:38 ` Paul Smith via Gdb
2025-05-28 7:33 ` Phi Debian via Gdb
2025-05-28 12:19 ` Eli Zaretskii via Gdb
2025-05-28 12:24 ` Guinevere Larsen via Gdb
2025-05-28 13:04 ` Paul Smith via Gdb
[not found] ` <CAJOr74gc9zeHQGST3eufT9zYJEsdEkO4m4xgxhQyQNE3kpSUNw@mail.gmail.com>
2025-05-29 9:16 ` Eli Zaretskii via Gdb
2025-05-28 7:44 ` Mark Wielaard
2025-05-28 12:30 ` Guinevere Larsen via Gdb
2025-05-30 11:22 ` Florian Weimer via Gdb
2025-05-30 20:39 ` Mark Wielaard
2025-05-28 11:47 ` Eli Zaretskii via Gdb
2025-05-28 11:39 ` Eli Zaretskii via Gdb
2025-05-28 12:15 ` Guinevere Larsen via Gdb [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=7bf8f6cc-2017-4cd4-9b74-bddaa4f1a4d3@redhat.com \
--to=gdb@sourceware.org \
--cc=eliz@gnu.org \
--cc=guinevere@redhat.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