From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [209.51.188.92]) by sourceware.org (Postfix) with ESMTPS id AC72D3858C2C for ; Thu, 10 Mar 2022 06:35:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org AC72D3858C2C Received: from [2001:470:142:3::e] (port=51220 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nSCP0-00037n-Ix; Thu, 10 Mar 2022 01:35:58 -0500 Received: from [87.69.77.57] (port=1120 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nSCP0-0000ky-0Q; Thu, 10 Mar 2022 01:35:58 -0500 Date: Thu, 10 Mar 2022 08:35:55 +0200 Message-Id: <83k0d2e2lw.fsf@gnu.org> From: Eli Zaretskii To: "Maciej W. Rozycki" Cc: gdb-patches@sourceware.org, simonsobisch@web.de, tom@tromey.com, aburgess@redhat.com In-Reply-To: (macro@embecosm.com) Subject: Re: [PATCH v4 7/8] GDB: Add a character string limiting option References: <83o82eewgh.fsf@gnu.org> X-Spam-Status: No, score=1.4 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_BARRACUDACENTRAL, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.4 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org 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: , X-List-Received-Date: Thu, 10 Mar 2022 06:36:01 -0000 > Date: Thu, 10 Mar 2022 00:03:47 +0000 (GMT) > From: "Maciej W. Rozycki" > cc: gdb-patches@sourceware.org, simonsobisch@web.de, > Tom Tromey , Andrew Burgess > > On Wed, 9 Mar 2022, Maciej W. Rozycki wrote: > > > > > +for when this option applies to strings. The value @code{unlimited} > > > > +causes there to be no limit. Related setting: @ref{set print elements}. > > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > This is not a very good idea. Texinfo is not HTML, so the results > > > produced for this in some formats will look awkward or even downright > > > incorrect English. It is better to use something like: > > > > > > @xref{set print elements}, for a related CLI command. > > > > Likewise. Thank you for your review. > > NB there are 21 preexisting cases of such phrasing across the GDB manual, > which you may want to (have people) clean up (yeah, a thought has struck > me I've seen this before, which is probably why Andrew copied it). Yes, I know. Thanks for making that point, I will add that to my todo.