From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Table cell refs with @0 or $0 are broken Date: Wed, 04 Apr 2012 13:17:54 -0400 Message-ID: <5119.1333559874@alphaville> References: <874nszzvoe.wl%jamshark70@dewdrop-world.net> Reply-To: nicholas.dokos@hp.com Return-path: Received: from eggs.gnu.org ([208.118.235.92]:38995) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SFTqW-0004Wy-6a for emacs-orgmode@gnu.org; Wed, 04 Apr 2012 13:18:17 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SFTqL-0007st-Lq for emacs-orgmode@gnu.org; Wed, 04 Apr 2012 13:18:11 -0400 Received: from g1t0027.austin.hp.com ([15.216.28.34]:30783) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SFTqL-0007p1-Fu for emacs-orgmode@gnu.org; Wed, 04 Apr 2012 13:18:01 -0400 In-Reply-To: Message from James Harkins of "Wed, 04 Apr 2012 17:35:29 +0800." <874nszzvoe.wl%jamshark70@dewdrop-world.net> 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: James Harkins Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org James Harkins wrote: > Don't know if this is fixed in a later org update, but -- the online > org manual says that you can refer to table cells in the current row > or column using @0 and $0 respectively, but that's definitely not > working on my machine. > > ** Works > | 1.0 | > | 2.0 | > | 3. | > #+TBLFM: @>$1=vsum(@1..@2) > > ** Broken: "Not in table data field" > | 1.0 | > | 2.0 | > | | > #+TBLFM: @>$1=vsum(@1$0..@2$0) > > It's not a critical issue because it does work to omit $0 -- so my > immediate problem is solved (getting the sum to calculate). But it > costs a little extra time because either a/ the manual is wrong or b/ > $0 is supposed to work and there's a bug. > Did this ever work? I've spot-checked back to 6.36c and I cannot find a release where it actually worked: assuming I haven't made a mistake, it seems to be an implementation oversight, rather than some patch specifically breaking the functionality. Nick