From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: variable names in manual Date: Fri, 26 Apr 2013 10:10:32 +0200 Message-ID: References: <94889.1366933045@greg-minshalls-mbp.local> <20130425234809.GC12340@kuru.dyndns-at-home.com> Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:53769) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UVdjv-0006YJ-Gr for emacs-orgmode@gnu.org; Fri, 26 Apr 2013 04:10:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UVdjn-0004mQ-Ho for emacs-orgmode@gnu.org; Fri, 26 Apr 2013 04:10:43 -0400 Received: from ezel.ic.uva.nl ([146.50.108.158]:45728) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UVdjn-0004mB-6K for emacs-orgmode@gnu.org; Fri, 26 Apr 2013 04:10:35 -0400 In-Reply-To: <20130425234809.GC12340@kuru.dyndns-at-home.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Suvayu Ali Cc: emacs-orgmode@gnu.org On 26 apr. 2013, at 01:48, Suvayu Ali = wrote: > On Thu, Apr 25, 2013 at 07:37:25PM -0400, Greg Minshall wrote: >> sorry about that. i was going to ask about the variable names in the >> current (8.x) documentation being in upper case. (then, wanted to = check >=20 > [...chomp...chomp...chomp...] >=20 >> but, it means that placing the cursor over the name and hitting C-h v >> doesn't default to that name. (and, i've always found that a = convenient >> way to navigate.) >>=20 >> so, just curious is it might make sense to revert to lower case = names. >=20 > I wasn't aware of this change! I would agree with Greg here. I suspect that the cases you are talking about here are due to incorrect use of the texinfo command @var{}. This should only be used for metasyntactical variables, when they stand for something else in a description.=20 Here is an example from the current manual. You can customize this behavior using the option @var{org-table-use-standard-references}.} to use another, more general representation that looks like this: @example @@@var{row}$@var{column} @end example The first use of @var is incorrect, @code should be used here. But the = use in @var{row} and @var{column} is correct. I believe that a while ago we did use @var and @code correctly, but = someone went through and changed the @code{org-...} to @var{org-...} at = some point. We need to change this back. - Carsten >=20 > --=20 > Suvayu >=20 > Open source is the future. It sets us free. >=20