From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [PATCH v2] POSIX ACL support Date: Wed, 05 Dec 2012 18:16:18 +0200 Message-ID: <83624gqxt9.fsf@gnu.org> References: <87zk1wxlto.fsf@silenus.orebokech.com> <837goxqhm2.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1354724235 13570 80.91.229.3 (5 Dec 2012 16:17:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 5 Dec 2012 16:17:15 +0000 (UTC) Cc: romain@orebokech.com, emacs-devel@gnu.org To: Glenn Morris Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 05 17:17:27 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1TgHf4-0001oh-4m for ged-emacs-devel@m.gmane.org; Wed, 05 Dec 2012 17:17:26 +0100 Original-Received: from localhost ([::1]:42184 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TgHer-0004bx-CD for ged-emacs-devel@m.gmane.org; Wed, 05 Dec 2012 11:17:13 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:45439) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TgHej-0004bl-Eh for emacs-devel@gnu.org; Wed, 05 Dec 2012 11:17:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TgHeZ-00062H-O3 for emacs-devel@gnu.org; Wed, 05 Dec 2012 11:17:05 -0500 Original-Received: from mtaout23.012.net.il ([80.179.55.175]:54719) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TgHeZ-000625-Fs; Wed, 05 Dec 2012 11:16:55 -0500 Original-Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0MEK00B00FO7A300@a-mtaout23.012.net.il>; Wed, 05 Dec 2012 18:16:17 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MEK00BSZFV54K70@a-mtaout23.012.net.il>; Wed, 05 Dec 2012 18:16:17 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.175 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:155298 Archived-At: > From: Glenn Morris > 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.