From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-refused-email@gnu.org>
Received: from fencepost.gnu.org (fencepost.gnu.org [IPv6:2001:470:142:3::e])
 by sourceware.org (Postfix) with ESMTPS id 03A3D395ACE6;
 Wed, 30 Jun 2021 15:43:11 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 03A3D395ACE6
Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3875
 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1lycMo-0006Op-Ba; Wed, 30 Jun 2021 11:43:10 -0400
Date: Wed, 30 Jun 2021 18:43:11 +0300
Message-Id: <83czs3mk8g.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Martin =?utf-8?Q?Li=C5=A1ka?= <mliska@suse.cz>
Cc: joseph@codesourcery.com, gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
In-Reply-To: <171356a6-5124-eb1a-17ab-b7c3dd6eb956@suse.cz> (message from
 Martin =?utf-8?Q?Li=C5=A1ka?= on Wed, 30 Jun 2021 16:04:32 +0200)
Subject: Re: [PATCH] Port GCC documentation to Sphinx
References: <1446990946.2994.192.camel@surprise>
 <e7f490fc-ab76-5bc5-5e94-1d9f00f34b62@suse.cz>
 <1a22bc37-3d48-132f-a3d5-219471cd443c@suse.cz>
 <3a2a573b-5185-fff5-f9da-6e5e39953ad6@suse.cz>
 <alpine.DEB.2.22.394.2106021645550.693958@digraph.polyomino.org.uk>
 <8641dc55-5412-fbd7-bafd-13604311f5ad@suse.cz>
 <alpine.DEB.2.22.394.2106101645050.424830@digraph.polyomino.org.uk>
 <e92d2ce5-59a0-ff65-bbfc-27072a452bfa@suse.cz>
 <alpine.DEB.2.22.394.2106111544150.479659@digraph.polyomino.org.uk>
 <5ffe3e32-ece0-a1b4-1fcf-e35177fa80b5@suse.cz>
 <alpine.DEB.2.22.394.2106231551380.13671@digraph.polyomino.org.uk>
 <87489d9a-44e2-411c-3f3a-534d07e78b95@suse.cz>
 <0866a0ea-c846-ea5e-ac7a-d1c8f106cc45@suse.cz>
 <5bb9a10d-f3b9-f16a-7430-bbae2d4978e2@suse.cz>
 <alpine.DEB.2.22.394.2106281533020.220739@digraph.polyomino.org.uk>
 <2f60f602-5d88-7674-9620-2172748664c5@suse.cz> <83a6n8obh4.fsf@gnu.org>
 <e00c7f70-b9e6-ac62-4982-75ea5c07c509@suse.cz> <83fswzmq0r.fsf@gnu.org> 
 <171356a6-5124-eb1a-17ab-b7c3dd6eb956@suse.cz>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=2.5 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS,
 TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Level: **
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: gcc@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc mailing list <gcc.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc>,
 <mailto:gcc-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <mailto:gcc-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc>,
 <mailto:gcc-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jun 2021 15:43:13 -0000

> Cc: joseph@codesourcery.com, gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
> From: Martin Liška <mliska@suse.cz>
> Date: Wed, 30 Jun 2021 16:04:32 +0200
> 
> > Thanks, but does that mean @var will no longer stand out in the
> > produced Info format?  That'd be sub-optimal, I think, because a clear
> > reference to a meta-syntactic variable will be lost.
> 
> Yes. An alternative approach for:
> Show :samp:`Samp with a {variable}.`
> 
> can be using @var{variable}, resulting with the following info output:
> Show ‘Samp with a VARIABLE.’
> 
> Does it seem reasonable?

Yes, the latter sounds reasonable.

Thanks.