From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id A1B923858C41 for ; Sun, 31 Mar 2024 05:01:20 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org A1B923858C41 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gnu.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gnu.org ARC-Filter: OpenARC Filter v1.0.0 sourceware.org A1B923858C41 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2001:470:142:3::10 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1711861282; cv=none; b=GSwRwqYtkDCDIxpRpClT/Sb4+jx9SA+1jrFhXYxbz98rL80o8xW1o3BjnZ99/KsIKpb4VSIU0ePpQjXhR7+TTh/zqWWrgMOtzI4+d2kJ5mDpLptNnpTa7GLC/PT1dJeuUYiGXaifuGrAmwuPJ2htH2aD7dVreLwkR57rCtKriCo= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1711861282; c=relaxed/simple; bh=rLLa/gDumi9/dhX+Ubb9FAynrbdT6vgK4a71ibKaN3s=; h=DKIM-Signature:Date:Message-Id:From:To:Subject:MIME-version; b=dBoWVyk2vdwKCV6XJM1ZrwX8NMN3YuMHwOSMQ3ubQqiWEErGDINdP46H1K2zvj1HIPlpKN/Rg8auhmw//YTIHKXxd8G0k1xy6RXZZaeJHa4HUvvL2ThbypyRPEcsM60e6tTPy0j6UsHF01MP60fkiNfa1peNngup/M3URbTbZ8Y= ARC-Authentication-Results: i=1; server2.sourceware.org Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rqnJn-000336-Qb; Sun, 31 Mar 2024 01:01:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=+Ahy58qcRhEqTysbg6eKjKxrF53Vn97wWVOK0vsIxPg=; b=lE9Bp2/XzMOCrSNJpyWY k+SrQIb+d5Z0KQ/5GBt4iUhNctSBApc8Upw1x7p0E1PnODceK5vc5wORVaETCr2jUvcvJlx6jxN7f 00MMOtNCdOkfW4ySrPc4RC6yfXoRsiUAYXj49a3jeDJk6ctmuA0l4IjOOggoP0vmtjLSPgLE5HrdD Dydsxl8OJsam19qsHA11FTtp1Wju5qXNpgydFfOhhIz1De2yaEqGbBmNUyYeoZlCT96j1C16CncM6 HK96THJ899kXupP39AadzfEEyvJXI4KwSOlLc9myCTkTw5Hdnw3a71NpgMlhoWeZVcRT0y7mmW00y pNz6GDcdjvTFfQ==; Date: Sun, 31 Mar 2024 08:01:16 +0300 Message-Id: <8634s7c7vn.fsf@gnu.org> From: Eli Zaretskii To: Tom Tromey Cc: gdb-patches@sourceware.org In-Reply-To: <20240330185401.1735449-1-tom@tromey.com> (message from Tom Tromey on Sat, 30 Mar 2024 12:54:01 -0600) Subject: Re: [PATCH] Normalize "on|off" text in manual References: <20240330185401.1735449-1-tom@tromey.com> MIME-version: 1.0 Content-type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.2 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: > From: Tom Tromey > Cc: Tom Tromey > Date: Sat, 30 Mar 2024 12:54:01 -0600 > > While looking in the info manual, I noticed this: > > ‘set style enabled ‘on|off’’ > > The styling looked weird here and in the source I saw it was written as: > > @item set style enabled @samp{on|off} > > I looked through the rest of the manual and found this same sort of > thing was written in a variety of styles. > > For this patch, I picked one way to write this and applied it to all > the instances. Thanks. I agree that we should be consistent. While using @r{..} for the brackets and "|" is probably rigorously correct, I think it is too much bother, and thus is likely not to be followed by many patches. I wonder whether we could use the simpler way: leave them alone, which will cause the entire "set style enabled on|off" have the @code markup, due to "@table @code". This will be easier to follow and easier to enforce. What do people think?