public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <andrew.burgess@embecosm.com>
Cc: gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: [PATCH 7/7] Add "set startup-quietly"
Date: Thu, 08 Oct 2020 09:44:54 +0300	[thread overview]
Message-ID: <83ft6p8bdl.fsf@gnu.org> (raw)
In-Reply-To: <c3f02cdd39a697015dc462b49ff6a254b2691110.1601927356.git.andrew.burgess@embecosm.com> (message from Andrew Burgess on Wed, 7 Oct 2020 21:05:11 +0100)

> From: Andrew Burgess <andrew.burgess@embecosm.com>
> Date: Wed,  7 Oct 2020 21:05:11 +0100
> Cc: Tom Tromey <tom@tromey.com>
> 
> +set startup-quietly on|off
> +show startup-quietly
> +  When enabled, this causes GDB to act as if "-silent" were always
> +  passed on the command line.  This saves the setting into a special
> +  configuration file, so that it can be read during startup and
> +  applied.

As I wrote earlier, the second sentence is inaccurate/incomplete.

> +@kindex set startup-quietly
> +@kindex show startup-quietly
> +This can also be enabled using @code{set startup-quietly on}.  The
> +default is @code{off}.  Use @code{show startup-quietly} to see the
> +current setting.  Changing this setting will cause it to automatically
> +be saved in a special configuration file, which is read by
> +@value{GDBN} early in its startup.

Likewise.  Also, the text should say explicitly that the setting will
not affect any aspect of GDB behavior during the current session.

> +The directory in which this file appears depends on the host platform.
> +On most systems, the file is in the @file{gdb} subdirectory of the
> +directory pointed to by the @env{XDG_CONFIG_HOME} environment
> +variable, if it is defined, else in the @file{.config/gdb}
> +subdirectory of your home directory.  However, on some systems, the
> +default may differ according to local convention.

Once again, this has been already documented elsewhere in the manual,
and in more detail.  Please leave here just the cross-reference to
that place, and please call that file "startup file", for consistency
with the terminology there.
> +  c = add_setshow_boolean_cmd ("startup-quietly", class_support,
> +			       &startup_quiet, _("\
> +Set whether GDB should start up quietly."), _("		\
> +Show whether GDB should start up quietly."), NULL,

I think the doc string should mention that the setting has no effect
in this session.

  reply	other threads:[~2020-10-08  6:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07 20:05 [PATCH 0/7] Adding startup files to GDB Andrew Burgess
2020-10-07 20:05 ` [PATCH 1/7] Add get_standard_config_dir function Andrew Burgess
2020-10-07 20:05 ` [PATCH 2/7] gdb: use get_standard_config_dir when looking for .gdbinit Andrew Burgess
2020-10-08  6:52   ` Eli Zaretskii
2020-11-02 10:20     ` Andrew Burgess
2020-10-22 19:07   ` Tom Tromey
2020-11-09 13:52   ` Tom Tromey
2020-11-09 13:55     ` Tom Tromey
2020-10-07 20:05 ` [PATCH 3/7] gdb: new function to wrap up executing command line scripts/commands Andrew Burgess
2020-10-08 15:25   ` Aktemur, Tankut Baris
2020-11-02  9:48     ` Andrew Burgess
2020-10-22 19:08   ` Tom Tromey
2020-10-07 20:05 ` [PATCH 4/7] gdb: process startup files and startup command line options Andrew Burgess
2020-10-08  6:28   ` Eli Zaretskii
2020-10-07 20:05 ` [PATCH 5/7] gdb: add mechanism to auto-save startup options Andrew Burgess
2020-10-08  6:36   ` Eli Zaretskii
2020-10-07 20:05 ` [PATCH 6/7] Let the user control the startup style Andrew Burgess
2020-10-08  6:40   ` Eli Zaretskii
2020-10-07 20:05 ` [PATCH 7/7] Add "set startup-quietly" Andrew Burgess
2020-10-08  6:44   ` Eli Zaretskii [this message]
2020-10-08  6:56 ` [PATCH 0/7] Adding startup files to GDB Eli Zaretskii
2020-10-22 19:02 ` Tom Tromey
2020-10-28 15:29   ` Andrew Burgess
2021-01-11 16:45   ` Andrew Burgess

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=83ft6p8bdl.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=andrew.burgess@embecosm.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).