unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
Cc: bob@rattlesnake.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: pxref
Date: Thu, 27 Oct 2005 21:06:00 +0200	[thread overview]
Message-ID: <upspqeq5j.fsf@gnu.org> (raw)
In-Reply-To: <200510271403.j9RE3eI02140@f7.net> (karl@freefriends.org)

> Date: Thu, 27 Oct 2005 09:03:40 -0500
> From: karl@freefriends.org (Karl Berry)
> Cc: rms@gnu.org, emacs-devel@gnu.org
> 
>     Specifically, in the new Info default, @xref does not always produce a
>     capitalized "See".  This means a change in documentation.
> 
> Sorry, I have no background for and don't understand any of this.  How
> can such a fundamental thing about Texinfo be changed?  Who did it and
> why?  Why should "Info" (do you mean info.el?) be downcasing/upcasing
> "See" (last I knew it was *[nN]ote" in Info, anyway, not "[sS]ee"])?
> 
> As far as I know neither makeinfo nor texinfo.tex have changed in this
> regard.  Also, it is not feasible to change texinfo.tex in any such way,
> if I'm understanding right.  (Messing with stuff based on surrounding
> text.)

Karl, you are absolutely right: there's no need to change anything in
Texinfo.  There's a huge misunderstanding here, mainly due to the fact
that Bob insists on saying that some ``new Info default'' changed what
@xref produces.

The reality is that @xref still produces the same output as it did
_in_the_Info_file, except that the Emacs Info reader displays the
leading "*Note" as "[Ss]ee", and hides the explicit reference to the
Info node and file, leaving just the reference name.  This was done to
make the cross-references look more like hyperlinks in other GUI
applications.

This is only a display trickery; info.el does not change the text read
from the Info file, it just uses the Emacs display features to display
certain text as a something different.  Thus, if one copies from the
buffer to another one, they will still see the same "*Note" and the
full cross-reference as makeinfo produces.

  parent reply	other threads:[~2005-10-27 19:06 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                             ` 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                                     ` Eli Zaretskii [this message]
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=upspqeq5j.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bob@rattlesnake.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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).