From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19635 invoked by alias); 22 Jun 2006 20:07:55 -0000 Received: (qmail 19627 invoked by uid 22791); 22 Jun 2006 20:07:54 -0000 X-Spam-Check-By: sourceware.org Received: from romy.inter.net.il (HELO romy.inter.net.il) (192.114.186.66) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 22 Jun 2006 20:07:53 +0000 Received: from HOME-C4E4A596F7 (IGLD-83-130-198-32.inter.net.il [83.130.198.32]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id EYO93712 (AUTH halo1); Thu, 22 Jun 2006 23:07:50 +0300 (IDT) Date: Thu, 22 Jun 2006 20:07:00 -0000 Message-Id: From: Eli Zaretskii To: gdb-patches@sourceware.org In-reply-to: <20060622033247.GA27704@nevyn.them.org> (message from Daniel Jacobowitz on Wed, 21 Jun 2006 23:32:47 -0400) Subject: Re: [rfc] Implementation of qXfer Reply-to: Eli Zaretskii References: <20060622033247.GA27704@nevyn.them.org> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-06/txt/msg00335.txt.bz2 > Date: Wed, 21 Jun 2006 23:32:47 -0400 > From: Daniel Jacobowitz > > Eli, I had to do something mildly surprising with texinfo xrefs: you can > reference an anchor which contains colons, but you have to use at least a > two-argument form of @xref. If you use the one-argument form, the "info" > browser will choke trying to parse it. I wanted to keep the anchor named > after the packet description it was attached to. Do the docs look OK? They are OK, except for this issue with anchors whose names contain a colon: this is against the Texinfo language rules. You might be lucky with a particular Info reader, but there are others out there, and each one of them uses a different method of searching for cross-reference names (some use fixed strings, others use various regular expressions). Using a colon makes them fail in different situations and in different interesting ways. So please let's remove the colons and use some other mnemonic methods to make the xref reflect the packet descriptor. > [I realize they may be a bit tricky to review; the qXfer docs are large, > and they replace the qPart docs but sit somewhere else in the alphabetical > list of packets. AFAICS, you just moved the text elsewhere and replaced qPart with qXfer, right? If there are new portions of text, please tell where they are.