Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii via Gdb <gdb@sourceware.org>
To: Phi Debian <phi.debian@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Improve GDB's first user experience by reducing "print_gdb_version" output
Date: Thu, 29 May 2025 12:16:37 +0300	[thread overview]
Message-ID: <86o6vbvksq.fsf@gnu.org> (raw)
In-Reply-To: <CAJOr74gc9zeHQGST3eufT9zYJEsdEkO4m4xgxhQyQNE3kpSUNw@mail.gmail.com> (message from Phi Debian on Thu, 29 May 2025 10:45:14 +0200)

> From: Phi Debian <phi.debian@gmail.com>
> Date: Thu, 29 May 2025 10:45:14 +0200
> 
> On Wed, May 28, 2025 at 2:20 PM Eli Zaretskii <eliz@gnu.org> wrote:
> 
>  > Date: Wed, 28 May 2025 09:33:09 +0200
> 
>  Unlike GDB, GCC is not an interactive program, so it produces this
>  information in the output of "gcc --version" and "gcc --help".
> 
> Ha Ok, I got it, yet I have hard time to find 'interactive program' that emit long copyright thing at start up.
> Looks like editors (vi, emacs) are also exempt of producing such copyright at start up.

Emacs does produce it by default, try "emacs -q" to see that.

  parent reply	other threads:[~2025-05-29  9: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 [this message]
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

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=86o6vbvksq.fsf@gnu.org \
    --to=gdb@sourceware.org \
    --cc=eliz@gnu.org \
    --cc=phi.debian@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