unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Eli Zaretskii <eliz@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 21:51:38 +0200	[thread overview]
Message-ID: <87mwzdufud.fsf@bzg.ath.cx> (raw)
In-Reply-To: <83txtlat5d.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 23 Oct 2012 21:24:30 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> This change is wrong:
>
>> === modified file 'doc/emacs/text.texi'
>> --- a/doc/emacs/text.texi	2012-06-17 05:13:40 +0000
>> +++ b/doc/emacs/text.texi	2012-10-23 16:12:59 +0000
>> @@ -1399,7 +1399,7 @@
>>  #+end_example
>>  @end example
>>  
>> -  For further details, see @ref{Exporting,,,org, The Org Manual} and
>> +  For further details, @pxref{Exporting,,,org, The Org Manual}, and
>>  @ref{Publishing,,,org, The Org Manual}.
>
> @pxref should only be used inside parentheses.  

Then (info "(texinfo)ref") is giving a misleading example:

8.6 `@ref'
==========

`@ref' is nearly the same as `@xref' except that it does not generate a
`See' in the printed output, just the reference itself.  This makes it
useful as the last part of a sentence.

For example,

     For more information, @pxref{This}, and @ref{That}.

> 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.                                   ^^^

-- 
 Bastien



  reply	other threads:[~2012-10-23 19:51 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 [this message]
2012-10-23 20:36     ` Eli Zaretskii
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=87mwzdufud.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=eliz@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).