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 B255239551CC
 for <gcc@gcc.gnu.org>; Tue, 13 Jul 2021 12:55:54 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B255239551CC
Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1392
 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 1m3Hx2-0006CP-Uj; Tue, 13 Jul 2021 08:55:53 -0400
Date: Tue, 13 Jul 2021 15:55:47 +0300
Message-Id: <83tuky8jak.fsf@gnu.org>
From: Eli Zaretskii <eliz@gnu.org>
To: Richard Biener <richard.guenther@gmail.com>
Cc: jwakely.gcc@gmail.com, gcc@gcc.gnu.org
In-Reply-To: <CAFiYyc2b9rVKCqjU1EyzVguZyhw2dsHkQwsY7pEm8RMg2cBeXg@mail.gmail.com>
 (message from Richard Biener on Tue, 13 Jul 2021 14:46:33 +0200)
Subject: Re: Benefits of using Sphinx documentation format
References: <1446990946.2994.192.camel@surprise> <83r1g3aady.fsf@gnu.org>
 <144d27f7-9486-0515-2ebd-4e8d9d9fc3b2@suse.cz> <4988937.164lfTNWpH@excalibur>
 <83k0lva2hv.fsf@gnu.org>
 <CAH6eHdTZs7VRh4oyNChCFET0qoVf3wSZZSeQhKWtb0cn=E2AvQ@mail.gmail.com>
 <CAFiYyc0HU-OVVavP0F1Pfu9WaKahp0NayGDBjjderoUaKn+BwA@mail.gmail.com>
 <83y2aa8m7g.fsf@gnu.org>
 <CAFiYyc2b9rVKCqjU1EyzVguZyhw2dsHkQwsY7pEm8RMg2cBeXg@mail.gmail.com>
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: Tue, 13 Jul 2021 12:55:56 -0000

> From: Richard Biener <richard.guenther@gmail.com>
> Date: Tue, 13 Jul 2021 14:46:33 +0200
> Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, GCC Development <gcc@gcc.gnu.org>
> I can very well understand the use of the html manual when you want
> to share pointers to specific parts of the documentation in communications.

In the Emacs community, we have a notation for a pointer to an Info
node FOO in the manual BAR that Emacs understands -- you just hit a
key, and Emacs lands you there.  So if you use the Emacs Info reader,
this issue doesn't exist.

> I'm also not sure if there's some texinfo URI that could be used to
> share documentation pointers.

Another Emacs command automatically produces a pointer to the current
node in an Info manuals in the above format.  So if I want to share a
pointer with you, I invoke that command, paste the result into an
email message, and you on your end invoke that other command.  Problem
solved.