From: Eli Zaretskii <eliz@gnu.org>
Cc: bug-texinfo@gnu.org, emacs-devel@gnu.org
Subject: Re: pxref
Date: Thu, 20 Oct 2005 11:29:22 +0200 [thread overview]
Message-ID: <uirvscz9p.fsf@gnu.org> (raw)
In-Reply-To: <17238.44739.179203.166568@kahikatea.snap.net.nz> (message from Nick Roberts on Thu, 20 Oct 2005 09:38:27 +1300)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Thu, 20 Oct 2005 09:38:27 +1300
>
> pxref seems to put in a full stop in the generated info page, when the
> reference includes the manual name:
>
> (@pxref{Registers,,, gdb, The GNU debugger}) gives: (see Registers(gdb).)
>
> which seems wrong since
>
> (@pxref{Registers}) gives: (see Registers)
Wrong mailing list ;-) It's not a Texinfo problem, it's a problem with
Emacs's reformatting of cross-references.
makeinfo _always_ produces either a "::" or a "." at the end of the
@pxref cross-reference, before the closing paren, because those are
the rules of the Info files. If you look in the emacs-* files with a
pager, you will see that a @pxref with more than one argument always
ends in a period, no matter if it's the in the same or another manual.
_______________________________________________
Texinfo home page: http://www.gnu.org/software/texinfo/
bug-texinfo@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-texinfo
next parent reply other threads:[~2005-10-20 9:29 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17238.44739.179203.166568@kahikatea.snap.net.nz>
2005-10-20 9:29 ` Eli Zaretskii [this message]
2005-10-20 11:16 ` pxref Juri Linkov
2005-10-20 12:41 ` pxref Eli Zaretskii
2005-10-20 16:46 ` pxref Juri Linkov
2005-10-20 19:35 ` pxref Eli Zaretskii
2005-10-23 4:42 ` pxref Richard M. Stallman
2005-10-23 7:27 ` pxref Eli Zaretskii
2005-10-23 13:43 ` pxref Robert J. Chassell
2005-10-23 16:14 ` pxref Eli Zaretskii
2005-10-23 20:20 ` pxref Robert J. Chassell
2005-10-23 22:45 ` pxref Eli Zaretskii
2005-10-24 13:38 ` pxref Richard M. Stallman
2005-10-24 20:17 ` pxref Robert J. Chassell
2005-10-26 16:46 ` pxref Richard M. Stallman
2005-10-26 18:29 ` pxref Robert J. Chassell
2005-10-26 18:34 ` pxref Robert J. Chassell
2005-10-26 19:02 ` pxref Robert J. Chassell
2005-10-26 20:55 ` pxref Robert J. Chassell
2005-10-26 20:57 ` pxref Karl Berry
2005-10-27 12:20 ` pxref Robert J. Chassell
2005-10-27 14:03 ` pxref Karl Berry
2005-10-27 15:03 ` pxref Robert J. Chassell
2005-10-27 15:29 ` pxref Karl Berry
2005-10-27 17:32 ` pxref Robert J. Chassell
2005-10-27 23:07 ` pxref Karl Berry
2005-10-28 8:28 ` pxref Eli Zaretskii
2005-10-29 2:24 ` pxref Luc Teirlinck
2005-10-29 19:47 ` pxref Juri Linkov
2005-11-08 20:59 ` pxref Kevin Rodgers
2005-11-09 9:34 ` pxref Juri Linkov
2005-11-09 19:27 ` pxref Kevin Rodgers
2005-11-10 1:39 ` pxref Miles Bader
2005-10-28 17:32 ` pxref Robert J. Chassell
2005-10-29 20:34 ` pxref Richard M. Stallman
2005-10-27 19:06 ` pxref Eli Zaretskii
2005-10-28 3:47 ` pxref Richard M. Stallman
2005-10-25 8:05 ` pxref Eli Zaretskii
2005-10-25 20:29 ` pxref Richard M. Stallman
2005-10-24 1:01 ` pxref Richard M. Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=uirvscz9p.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bug-texinfo@gnu.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).