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 19BE73886C5C;
 Mon, 12 Jul 2021 14:16:22 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 19BE73886C5C
Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1637
 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 1m2wjN-0000PE-DT; Mon, 12 Jul 2021 10:16:21 -0400
Date: Mon, 12 Jul 2021 17:16:15 +0300
Message-Id: <83pmvnaa8g.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: mliska@suse.cz, gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org,
 joseph@codesourcery.com
In-Reply-To: <CAH6eHdQvwNpzDRoLHTKbt6oSuwKj8cN6pYtZ9TaUejdhPoeZKw@mail.gmail.com>
 (message from Jonathan Wakely on Mon, 12 Jul 2021 15:05:11 +0100)
Subject: Re: Benefits of using Sphinx documentation format
References: <1446990946.2994.192.camel@surprise>
 <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>
 <57743e51-04d5-ec2e-b684-54f0321ef0bd@suse.cz> <83pmw3mrcg.fsf@gnu.org>
 <alpine.BSF.2.20.16.2107021942320.92378@arjuna.pair.com>
 <98388e12-3712-575b-9387-45b6ea7ef498@suse.cz>
 <83v95fabwx.fsf@gnu.org>
 <CAH6eHdRRHoyDr_R3Df19MdM77+PXqrGdVgv_GzCXZUx38umwMA@mail.gmail.com>
 <CAH6eHdQvwNpzDRoLHTKbt6oSuwKj8cN6pYtZ9TaUejdhPoeZKw@mail.gmail.com>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=2.2 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS,
 TXREP 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: 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: Mon, 12 Jul 2021 14:16:23 -0000

> From: Jonathan Wakely <jwakely.gcc@gmail.com>
> Date: Mon, 12 Jul 2021 15:05:11 +0100
> Cc: Martin Liška <mliska@suse.cz>, 
> 	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, gcc-patches <gcc-patches@gcc.gnu.org>, 
> 	"Joseph S. Myers" <joseph@codesourcery.com>
> 
> To be clear, I give links to users frequently (several times a week,
> every week, for decades) and prefer to give them a link to specific
> options. Obviously I link to the online HTML docs rather than telling
> them an 'info' command to run, because most people don't use info
> pages or know how to navigate them. That means I can't provide decent
> links, because the actual option name I'm trying to link to is always
> off the top of the page. This is simply unacceptable IMHO. Texinfo
> must go.

"Texinfo must go" is one possible conclusion from your description.
But it isn't the only one.  An alternative is "the Texinfo source of
the GCC manual must be improved to fix this problem."  And yes, this
problem does have a solution in Texinfo.