Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tom@tromey.com, gdb-patches@sourceware.org
Subject: Re: [PATCHv3 3/3] gdb: add "set startup-quietly" command
Date: Wed, 24 Mar 2021 12:08:36 +0000	[thread overview]
Message-ID: <20210324120836.GK5520@embecosm.com> (raw)
In-Reply-To: <8335xt5ljk.fsf@gnu.org>

* Eli Zaretskii <eliz@gnu.org> [2021-02-18 19:32:31 +0200]:

> > From: Andrew Burgess <andrew.burgess@embecosm.com>
> > Date: Thu, 18 Feb 2021 16:41:04 +0000
> > Cc: Tom Tromey <tom@tromey.com>
> > 
> > gdb/ChangeLog:
> > 
> > 	* NEWS: Add entry.
> > 	* main.c (captured_main_1): Call check_quiet_mode.
> > 	* top.c (startup_quiet): New global.
> > 	(check_quiet_mode): New function.
> > 	(show_startup_quiet): New function.
> > 	(init_main): Register new command.
> > 	* top.h (check_quiet_mode): Declare.
> > 
> > gdb/doc/ChangeLog:
> > 
> > 	* gdb.texinfo (Mode Options): Mention "set startup-quietly".
> > 
> > gdb/testsuite/ChangeLog:
> > 
> > 	* gdb.base/startup-file.exp: Add more tests.
> 
> The documentation parts are okay, except that...
> 
> > +set startup-quietly on|off
> > +show startup-quietly
> > +  When 'on', this causes GDB to act as if "-silent" were passed on the
> > +  command line.  This command needs to be added to an early
> > +  initialization file (e.g. ~/.config/gdb/gdbearlyinit) in order to
> > +  affect GDB.                             ^^^^^^^^^^^^
> > [...]
> > +Set whether GDB should start up quietly."), _("		\
> > +Show whether GDB should start up quietly."), _("\
> > +This setting will not affect the current session.  Instead this command\n\
> > +should be added to the .gdbstartup file in the users home directory to\n\
>                           ^^^^^^^^^^^
> 
> ...there seems to be a disagreement regarding the name of that early
> initialization file.

Thanks, I have fixed this in my local branch.

Andrew

  reply	other threads:[~2021-03-24 12:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26  9:48 [PATCHv2 0/3] Adding startup files to GDB Andrew Burgess
2021-01-26  9:48 ` [PATCHv2 1/3] gdb: refactor the initialization file lookup code Andrew Burgess
2021-01-26 15:09   ` Simon Marchi via Gdb-patches
2021-01-26  9:48 ` [PATCHv2 2/3] gdb: process startup files and startup command line options Andrew Burgess
2021-01-26 15:22   ` Eli Zaretskii via Gdb-patches
2021-01-26 15:32     ` Simon Marchi via Gdb-patches
2021-01-26 15:30   ` Simon Marchi via Gdb-patches
2021-01-26  9:48 ` [PATCHv2 3/3] gdb: add "set startup-quietly" command Andrew Burgess
2021-01-26 15:12   ` Eli Zaretskii via Gdb-patches
2021-02-18 16:41 ` [PATCHv3 0/3] Adding startup files to GDB Andrew Burgess
2021-02-18 16:41   ` [PATCHv3 1/3] gdb: refactor the initialization file lookup code Andrew Burgess
2021-02-18 16:41   ` [PATCHv3 2/3] gdb: process early initialization files and command line options Andrew Burgess
2021-02-18 17:46     ` Eli Zaretskii via Gdb-patches
2021-03-24 12:10       ` Andrew Burgess
2021-03-24 17:17         ` Eli Zaretskii via Gdb-patches
2021-02-18 16:41   ` [PATCHv3 3/3] gdb: add "set startup-quietly" command Andrew Burgess
2021-02-18 17:32     ` Eli Zaretskii via Gdb-patches
2021-03-24 12:08       ` Andrew Burgess [this message]
2021-03-31 20:11   ` [PATCHv3 0/3] Adding startup files to GDB Andrew Burgess
2021-04-02 19:20     ` Tom Tromey

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=20210324120836.GK5520@embecosm.com \
    --to=andrew.burgess@embecosm.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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