From: Eli Zaretskii via Gdb <gdb@sourceware.org>
To: Guinevere Larsen <guinevere@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Improve GDB's first user experience by reducing "print_gdb_version" output
Date: Wed, 28 May 2025 14:39:00 +0300 [thread overview]
Message-ID: <86plftvuaz.fsf@gnu.org> (raw)
In-Reply-To: <0bfd51f7-2246-475c-b171-8dde8474227a@redhat.com> (message from Guinevere Larsen via Gdb on Tue, 27 May 2025 17:43:18 -0300)
> 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".
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.
next prev parent reply other threads:[~2025-05-28 11:39 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 [this message]
2025-05-28 12:15 ` Guinevere Larsen via Gdb
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=86plftvuaz.fsf@gnu.org \
--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