From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id nahLBmsxEGBJLAAAWB0awg (envelope-from ) for ; Tue, 26 Jan 2021 10:12:43 -0500 Received: by simark.ca (Postfix, from userid 112) id 0D1621EF80; Tue, 26 Jan 2021 10:12:43 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 59A651E945 for ; Tue, 26 Jan 2021 10:12:42 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 076353846401; Tue, 26 Jan 2021 15:12:42 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 076353846401 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1611673962; bh=EH9v9C/VryfdIEeCrmh2Q/1HQufn1s2+2yw6GPXQ/a8=; h=Date:To:In-Reply-To:Subject:References:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=gChVvPj4i/Syypfk9IjGm1WEhivUu6XdG8YjYpZqd4wnY5iZB3Y4P4fZgj6DE3m84 SWb9x1LUVupMOOKgd+Wm/fm49zhyI6UckStD2BrKDMZfSR0i1doVfs2xCNG/PGn6Vs d0eW3nxgxhoQtOuPE5reDVmu5939WaPtn23HAVoU= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 188AF3861841 for ; Tue, 26 Jan 2021 15:12:40 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 188AF3861841 Received: from fencepost.gnu.org ([2001:470:142:3::e]:52383) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l4Q1H-0006c4-Gk; Tue, 26 Jan 2021 10:12:39 -0500 Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3212 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1l4Q1E-0007rA-NO; Tue, 26 Jan 2021 10:12:37 -0500 Date: Tue, 26 Jan 2021 17:12:44 +0200 Message-Id: <83ft2n20lv.fsf@gnu.org> To: Andrew Burgess In-Reply-To: (message from Andrew Burgess on Tue, 26 Jan 2021 09:48:13 +0000) Subject: Re: [PATCHv2 3/3] gdb: add "set startup-quietly" command References: X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Eli Zaretskii via Gdb-patches Reply-To: Eli Zaretskii Cc: tom@tromey.com, gdb-patches@sourceware.org Errors-To: gdb-patches-bounces@sourceware.org Sender: "Gdb-patches" > From: Andrew Burgess > Date: Tue, 26 Jan 2021 09:48:13 +0000 > Cc: Tom Tromey > > From: Tom Tromey > > This adds a new command to change GDB to behave as though "-quiet" > were always given. This new command can be added to the gdbstartup > file to affect future GDB sessions. > > 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. Thanks. > +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 command needs to be added to a > + gdbstartup file in order to affect GDB. What is "gdbstartup file"? Also, the manual seems to describe the use of this feature differently: > +@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 have no affect on the > +current @value{GDBN} session. Add @code{set startup-quietly on} to > +the startup command file (@pxref{Initialization Files,,Initialization > +Files}) to affect future @value{GDBN} sessions. Why is there a difference between the two descriptions? Also, the sentence starting with "Changing this setting will have" is slightly confusing, because it is not absolutely clear that it refers only to the "set" command issued from the CLI, and does NOT affect the startup file setting. Could you please clarify this text?