From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Schulte Subject: Re: Standardized code block syntax and Property Accumulation merged into Master Date: Thu, 17 Nov 2011 09:15:11 -0700 Message-ID: <87mxbud8j8.fsf@gmail.com> References: <877h31nzrg.fsf@gmail.com> <80r516annk.fsf@somewhere.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([140.186.70.92]:39506) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RR4iX-0001VO-NO for emacs-orgmode@gnu.org; Thu, 17 Nov 2011 11:21:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RR4iW-0001Ej-4y for emacs-orgmode@gnu.org; Thu, 17 Nov 2011 11:21:37 -0500 Received: from mail-iy0-f169.google.com ([209.85.210.169]:50099) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RR4iW-0001EX-1s for emacs-orgmode@gnu.org; Thu, 17 Nov 2011 11:21:36 -0500 Received: by iaek3 with SMTP id k3so2884640iae.0 for ; Thu, 17 Nov 2011 08:21:35 -0800 (PST) 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: Sebastien Vauban Cc: emacs-orgmode@gnu.org "Sebastien Vauban" writes: > Hi Eric, > > Eric Schulte wrote: >> The standard-code-block-syntax branch has been merged into the master branch >> of the git repository. [...] Additionally I've updated my collection of >> Org-mode code block scraps [4]. >> >> [4] http://eschulte.github.com/org-scraps/ > > I just looked at a couple of them, and it occurred to me that this one can't > work (anymore?) as the name of the *data* table is the same as the name of the > *source* block: > > http://eschulte.github.com/org-scraps/scraps/2011-08-19-replacing-a-table.html > Indeed, this change actually isn't directly related to the syntax changes but is rather a result of a recent bug fix, as whenever there are both data and code with the same name, the code should be primary because the data could simply be un-cached results of the code. > > Changing one name or the other does cure this. > Thanks, I've simply removed this example. Cheers -- Eric > > Best regards, > Seb -- Eric Schulte http://cs.unm.edu/~eschulte/