From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26783 invoked by alias); 6 Sep 2011 20:01:18 -0000 Received: (qmail 26769 invoked by uid 22791); 6 Sep 2011 20:01:17 -0000 X-SWARE-Spam-Status: No, hits=-1.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_SOFTFAIL X-Spam-Check-By: sourceware.org Received: from mtaout21.012.net.il (HELO mtaout21.012.net.il) (80.179.55.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 06 Sep 2011 20:00:59 +0000 Received: from conversion-daemon.a-mtaout21.012.net.il by a-mtaout21.012.net.il (HyperSendmail v2007.08) id <0LR400G009XXDM00@a-mtaout21.012.net.il> for gdb-patches@sourceware.org; Tue, 06 Sep 2011 23:00:11 +0300 (IDT) Received: from HOME-C4E4A596F7 ([84.229.83.44]) by a-mtaout21.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0LR400G48A896L90@a-mtaout21.012.net.il>; Tue, 06 Sep 2011 23:00:10 +0300 (IDT) Date: Tue, 06 Sep 2011 20:07:00 -0000 From: Eli Zaretskii Subject: Re: Doc: make python function/method descriptions look as in Python In-reply-to: <09787EF419216C41A903FD14EE5506DD0153491A82@AUSX7MCPC103.AMER.DELL.COM> To: Paul_Koning@Dell.com Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org Reply-to: Eli Zaretskii Message-id: <8362l5jvao.fsf@gnu.org> References: <09787EF419216C41A903FD14EE5506DD015343BFAE@AUSX7MCPC103.AMER.DELL.COM> <837h5p2a6g.fsf@gnu.org> <09787EF419216C41A903FD14EE5506DD01534911A3@AUSX7MCPC103.AMER.DELL.COM> <09787EF419216C41A903FD14EE5506DD01534916A6@AUSX7MCPC103.AMER.DELL.COM> <09787EF419216C41A903FD14EE5506DD0153491A82@AUSX7MCPC103.AMER.DELL.COM> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2011-09/txt/msg00098.txt.bz2 > From: > CC: > Date: Tue, 6 Sep 2011 14:39:36 -0500 > > Thanks! > > I spotted one problem. Changing the description of gdb.prompt_hook from a defop to a defun made the xref{prompt_hook} not work. Either that or it was broken already. I made it xref{gdb.prompt_hook} but that produces an error when I click on that cross-reference. What's the texinfo magic to define what xref points to? That magic is @anchor, but you broke it because you changed the name of the anchor, which you shouldn't: > -@defop Operation {@value{GDBN}} prompt_hook current_prompt > -@anchor{prompt_hook} > +@defun gdb.prompt_hook (current_prompt) > +@anchor{gdb.prompt_hook} You shouldn't change the @anchor line at all, because its label has nothing to do with the method name. It's just a label, is not visible to the reader, and it _must_ match the label inside @xref. You cannot change one without changing the other to match.