all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Robert J. Chassell" <bob@rattlesnake.com>
Cc: karl@freefriends.org, emacs-devel@gnu.org
Subject: Re: pxref
Date: Wed, 26 Oct 2005 19:02:50 +0000 (UTC)	[thread overview]
Message-ID: <m1EUqXy-0004RGC@rattlesnake.com> (raw)
In-Reply-To: <E1EUoQ2-0006IX-46@fencepost.gnu.org> (rms@gnu.org)

Today's GNU Emacs CVS snapshot, Wed, 2005 Oct 26  17:49 UTC
GNU Emacs 22.0.50.6 (i686-pc-linux-gnu, GTK+ Version 2.6.10)
started with `emacs -Q -D'

"Richard M. Stallman" <rms@gnu.org> wrote,

   I installed a fix I think is correct.

The change for Info looks correct to me.  I added more test lines to
foo.texi and they all look right in the default Emacs Info.

(When I set `Info-hide-note-references' to nil, as I do customarily, 
the cross references are shown by `*note' and `*Note' in a manner that
is correct.) 

However, using `xdvi', I also checked the DVI version that was created
with `texi2dvi' (GNU Texinfo 4.8) 1.34.  Unfortunately, the typeset
output displays a capitalized `See' when the preceding text both ends
with a colon and is not followed by a blank line.

Karl Berry, what do you see?

In DVI as viewed with xdvi:

    Here is another @xref, no parentheses; this ends with a colon and
    is not followed by a blank line: See Musings on fossil fuels.

(Note also the one space before the `See'; this is correct for
typesetting according to my copy of the Chicago Manual of Style,
although when I type, I tend to put in two spaces.  The Texinfo source
has two spaces.)

But in the default Info display:

    Here is another @xref, no parentheses; this ends with a colon and
    is not followed by a blank line:  see Musings on fossil fuels.

(Note the two spaces before the `see', which looks right to me.)

Here is the test file I used:


\input texinfo.tex  @c -*-texinfo-*-
@comment %**start of header
@setfilename foo.info
@settitle Texinfo Test
@smallbook
@comment %**end of header

@ignore

 ## Summary of shell commands to create various output formats:

    pushd /u/texinfo/

    ## Info output
    makeinfo --force --fill-column=70 --no-split --paragraph-indent=0 \
    --verbose foo.texi

    ## ;; (kill-buffer "*info*")
    ## ;; (info "/u/texinfo/foo.info" nil)

    ## DVI output
    texi2dvi foo.texi

    ## View DVI output
    ##     xdvi foo.dvi &

    ## HTML output
    makeinfo --no-split --html foo.texi

    ## Plain text output
    makeinfo --fill-column=70 --no-split --paragraph-indent=0 \
    --verbose --no-headers --output=foo.txt  \
    foo.texi


    ## DocBook output
    makeinfo --docbook --no-split --paragraph-indent=0 \
    --verbose foo.texi

    ## XML output
    makeinfo --xml --no-split --paragraph-indent=0 \
    --verbose foo.texi

    popd

@end ignore

@titlepage
@sp 6
@center @titlefont{Test document}
@sp 4
@center by Robert J. Chassell

@page
@vskip 0pt plus 1filll
@end titlepage

@contents

@ifnottex
@node Top, Chapter One, (dir), (dir)
@top Test Top
@end ifnottex

@menu
* Chapter One::
* Musings on fossil fuels::
@end menu

@node Chapter One, Musings on fossil fuels, Top, Top
@chapter Chapter One

Contents of chapter 1.
@sp 1

@ifnotinfo
@noindent
@end ifnotinfo
See
@ifnotinfo

@noindent
@end ifnotinfo
@url{http://www.rattlesnake.com/notions/Choice-and-Constraint.html},
@ifnotinfo

@noindent
@end ifnotinfo
which is intended as a description of `what is'
@dots{} not the `what is' that most often concern citizens,
politicians, and political scientists, but a `what is' that reflects
the current world and of `what can be done'.

@sp 1

    Here is an @@pxref (@pxref{Musings on fossil fuels}) in a sentence.

    Here is a standalone xref within parentheses:

    (@xref{Musings on fossil fuels}.)

    Here is another @@xref, no parentheses; this ends with a colon and
    is followed by a blank line:

    @xref{Musings on fossil fuels}.

    Here is another @@xref, no parentheses; this ends with a period and
    is followed by a blank line.

    @xref{Musings on fossil fuels}.


    Here is another @@xref, no parentheses; this ends with a colon and
    is not followed by a blank line:  @xref{Musings on fossil fuels}.

    Here is another @@xref, no parentheses; this ends with a period and
    is not followed by a blank line.  @xref{Musings on fossil fuels}.

    Here is a standalone xref within parentheses, no blank line:
    (@xref{Musings on fossil fuels}.)


@sp 1
More contents of chapter 1.


@node Musings on fossil fuels,  , Chapter One, Top
@chapter Musings on Fossil Fuels

More than three decades ago, some modern people I knew tried to
replace fossil fuels with alternate sources of energy.

@bye


-- 
    Robert J. Chassell                         
    bob@rattlesnake.com                         GnuPG Key ID: 004B4AC8
    http://www.rattlesnake.com                  http://www.teak.cc

  parent reply	other threads:[~2005-10-26 19:02 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 ` pxref Eli Zaretskii
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                             ` Robert J. Chassell [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1EUqXy-0004RGC@rattlesnake.com \
    --to=bob@rattlesnake.com \
    --cc=emacs-devel@gnu.org \
    --cc=karl@freefriends.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.