Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Guinevere Larsen via Gdb <gdb@sourceware.org>
To: Mark Wielaard <mark@klomp.org>, psmith@gnu.org
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Improve GDB's first user experience by reducing "print_gdb_version" output
Date: Wed, 28 May 2025 09:30:17 -0300	[thread overview]
Message-ID: <7c0851e0-f62d-491e-b59a-33452f9eab9a@redhat.com> (raw)
In-Reply-To: <20250528074401.GG11631@gnu.wildebeest.org>

On 5/28/25 4:44 AM, Mark Wielaard wrote:
> Hi,
>
> On Tue, May 27, 2025 at 05:38:57PM -0400, Paul Smith via Gdb wrote:
>> On Tue, 2025-05-27 at 17:43 -0300, Guinevere Larsen via Gdb wrote:
>>> I'm sending this here in case there is some rule that forces us to
>>> write the copyright or free software status at initialization, before
>>> spending the time to turn this into a patch.
>> I had remembered that interactive programs should generate copyright
>> information at startup, but the most I can find in the current GNU
>> Maintainer's manual is
> The GPL itself contains the recommendation at the end (after the
> actual terms and conditions) in the section "How to Apply These Terms
> to Your New Programs". It is even shorter than Guinevere's suggestion,
> it recommends outputting just 4 lines:

While shorter than my suggestion, it doesn't add any of the helpful 
things that a new user would want to know about GDB specifically, so we 
would need a couple more lines anyway.

Considering that the license says "output a short notice *like* this" 
(emphasis mine), I would imagine we can alter it without trouble. In 
fact, on a first invocation of emacs, I'm greeted with only a screen 
that looks very different to that message, starting by welcoming users, 
offering a tutorial, a guided tour and a link to the manual before 
mentioning copyright or warranty, which is much friendlier to someone 
attempting to learn to use it on their own.

-- 
Cheers,
Guinevere Larsen
She/Her/Hers

>
>    If the program does terminal interaction, make it output a short
>    notice like this when it starts in an interactive mode:
>
>      <program>  Copyright (C) <year>  <name of author>
>      This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
>      This is free software, and you are welcome to redistribute it
>      under certain conditions; type `show c' for details.
>
>    The hypothetical commands `show w' and `show c' should show the
>    appropriate parts of the General Public License.  Of course, your
>    program's commands might be different; for a GUI interface, you
>    would use an "about box".
>
> Cheers,
>
> Mark
>


  reply	other threads:[~2025-05-28 12:31 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 [this message]
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

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=7c0851e0-f62d-491e-b59a-33452f9eab9a@redhat.com \
    --to=gdb@sourceware.org \
    --cc=guinevere@redhat.com \
    --cc=mark@klomp.org \
    --cc=psmith@gnu.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