unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Bastien <bzg@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] /srv/bzr/emacs/trunk r110632: * text.texi (Org Authoring): Change @ref to @pxref.
Date: Tue, 23 Oct 2012 22:36:07 +0200	[thread overview]
Message-ID: <83pq49apu0.fsf@gnu.org> (raw)
In-Reply-To: <87mwzdufud.fsf@bzg.ath.cx>

> From: Bastien <bzg@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Tue, 23 Oct 2012 21:51:38 +0200
> 
> > @pxref should only be used inside parentheses.  
> 
> Then (info "(texinfo)ref") is giving a misleading example:

Indeed, it does.  The next node in the Texinfo manual says:

  The parenthetical reference command, `@pxref', is nearly the same as
  `@xref', but it is best used at the end of a sentence or before a
  closing parenthesis.

The place where you used it is neither of these two.

> > What was the problem with "see @ref", apart of the fact that a comma
> > was missing after the closing brace?
> 
> The period after the first ref@{...} in the info documentation.
> 
> See at the end of (info "(emacs)Org Authoring"):
> 
>    For further details, see *note Exporting: (org)Exporting. and *note Publishing:
>  (org)Publishing.                                   ^^^

If I add a comma after the first @ref, like this:

    For further details, see @ref{Exporting,,,org, The Org Manual}, and
  @ref{Publishing,,,org, The Org Manual}.                        ^^^

there's no period in the Info output:

     For further details, see *note Exporting: (org)Exporting, and *note
  Publishing: (org)Publishing.



  reply	other threads:[~2012-10-23 20:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.690771.1351016269.854.emacs-diffs@gnu.org>
2012-10-23 19:24 ` [Emacs-diffs] /srv/bzr/emacs/trunk r110632: * text.texi (Org Authoring): Change @ref to @pxref Eli Zaretskii
2012-10-23 19:51   ` Bastien
2012-10-23 20:36     ` Eli Zaretskii [this message]
2012-10-23 21:27       ` Bastien

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=83pq49apu0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=bzg@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).