From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id OINWOe0LlmLPeAkAWB0awg (envelope-from ) for ; Tue, 31 May 2022 08:37:01 -0400 Received: by simark.ca (Postfix, from userid 112) id E616D1E221; Tue, 31 May 2022 08:37:01 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=ury6Toqc; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (ip-8-43-85-97.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 F38B31E00D for ; Tue, 31 May 2022 08:37:00 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 763403839C69 for ; Tue, 31 May 2022 12:37:00 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 763403839C69 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1654000620; bh=7xlOqBgfxBPQ6QlGmIHEl5FSY7oFREvR80URJWMDIBw=; 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=ury6ToqcYK0lx/aWnDO2bJk++dTAQT9nbQKBKJgVOzElLcKZAobX0846n8VBqS8BZ s5RqAlcMjfVBjJAIB7e4zkuXruJlXYePso63vu0+F/kVhjdxnhKOihgE1wqlUGkkHY 4Ee4YnQ6vFSnnBHvtMWsIhZ5iUo4MvGCoV+No1a0= Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 28B753856DFB for ; Tue, 31 May 2022 12:36:41 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 28B753856DFB Received: from fencepost.gnu.org ([2001:470:142:3::e]:36148) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nw171-0007j3-Ug; Tue, 31 May 2022 08:36:39 -0400 Received: from [87.69.77.57] (port=2263 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 1nw16l-0007Mn-QO; Tue, 31 May 2022 08:36:37 -0400 Date: Tue, 31 May 2022 15:36:28 +0300 Message-Id: <83k0a1j2ur.fsf@gnu.org> To: Pedro Alves In-Reply-To: (message from Pedro Alves on Tue, 31 May 2022 12:05:53 +0100) Subject: Re: [PATCH] Improve clear command's documentation References: <20220526194250.2310460-1-pedro@palves.net> <838rqmm7gb.fsf@gnu.org> <6914f754-4e33-5aa1-4ea6-dca9504e8bfe@palves.net> <837d63j8tx.fsf@gnu.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: , From: Eli Zaretskii via Gdb-patches Reply-To: Eli Zaretskii Cc: gdb-patches@sourceware.org Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" > Date: Tue, 31 May 2022 12:05:53 +0100 > Cc: gdb-patches@sourceware.org > From: Pedro Alves > > How about this, basically a complete rewrite of the clear command's > documentation: Thanks, the idea to rewrite it is indeed a good one. But the actual text IMO came out highly repetitive, and has several markup issues. Rather than commenting on each issue, I suggest the following reworded text: @item clear @var{locspec} Delete any breakpoint whose code location corresponds to @var{locspec}. @xref{Location Specifications}, for the various forms of @var{locspec}. Which code locations correspond to @var{locspec} depends on the form used in the location specifications @var{locspec}: @table @code @item @var{linenum} @itemx @var{filename}:@var{linenum} @itemx -line @var{linenum} @itemx -source @var{filename} -line @var{linenum} If @var{locspec} specifies a line number, with or without a file name, the command deletes any breakpoint whose code location is at or within the specified line @var{linenum} in files that match the specified @var{filename}. If @var{filename} is omitted, it defaults to the current source file. @item *@var{address} If @var{locspec} specifies an address, the command deletes any breakpoint whose code location is at the given @var{address}. @item @var{function} @itemx -function @var{function} If @var{locspec} specifies a function, the command deletes any breakpoint whose code location is at the entry to any function whose name matches @var{function}. @end table Ambiguity in names of files and functions can be resolved as described in @ref{Location Specifications}. WDYT?