From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: romain@orebokech.com, emacs-devel@gnu.org
Subject: Re: [PATCH v2] POSIX ACL support
Date: Wed, 05 Dec 2012 18:16:18 +0200 [thread overview]
Message-ID: <83624gqxt9.fsf@gnu.org> (raw)
In-Reply-To: <ghsj7lcf7k.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Cc: romain@orebokech.com, emacs-devel@gnu.org
> Date: Tue, 04 Dec 2012 23:09:35 -0500
>
> Eli Zaretskii wrote:
>
> > While @pxref will work, it is better not to use it except in
> > parentheses.
>
> FWIW, I disagree
With which part? I didn't say @pxref will not work. If you think it
is better than "see @ref", please tell why.
> (and the Texinfo manual doesn't seem to agree with you
> either AFAICS).
That depends on the version of Texinfo. The one for version 4.8
(which we support) still says
8.7 `@pxref'
============
The parenthetical reference command, `@pxref', is nearly the same as
`@xref', but you use it _only_ inside parentheses and you do _not_ type
a comma or period (or anything else) after the command's closing brace.
I don't understand why later versions now say
In general, it is best to use `@ref' only when you need some word
other than "see" to precede the reference. When "see" (or "See") is
ok, `@xref' and `@pxref' are preferable.
But they still say
8.7 `@pxref'
============
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.
IOW, the "parenthetical" part is kept, so saying it is preferable
outside of parens makes little sense to me. (It makes even less sense
to work against my muscle memory, but that's another story.)
The problem is that people who use Texinfo only very rarely tend to
become confused about the precise use cases covered by each of the
*ref directives, and since 'p' stands for "parenthetical", telling
them to use it only in parens helps them remember. And since both
forms work in this particular case, I think @pxref is better.
next prev parent reply other threads:[~2012-12-05 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-02 20:04 [PATCH v2] POSIX ACL support Romain Francoise
2012-12-04 20:42 ` Eli Zaretskii
2012-12-06 19:45 ` Romain Francoise
2012-12-07 8:19 ` Michael Albinus
2012-12-07 9:32 ` Eli Zaretskii
2012-12-05 2:28 ` Glenn Morris
2012-12-05 3:53 ` Eli Zaretskii
2012-12-05 4:09 ` Glenn Morris
2012-12-05 16:16 ` Eli Zaretskii [this message]
2012-12-05 17:18 ` Glenn Morris
2012-12-06 19:48 ` Romain Francoise
2012-12-06 21:33 ` Stefan Monnier
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=83624gqxt9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=romain@orebokech.com \
/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.