From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Moe Subject: Re: [RFC] Standardized code block keywords Date: Fri, 21 Oct 2011 09:26:31 +0200 Message-ID: <4EA11EA7.7020501@christianmoe.com> References: <87pqhrih3s.fsf@gmail.com> <30891.1319141196@alphaville.dokosmarshall.org> <87fwinifqu.fsf@gmail.com> <32184.1319143892@alphaville.dokosmarshall.org> <808vofwf1w.fsf@somewhere.org> <87y5wfgwn7.fsf_-_@gmail.com> <8895.1319165867@alphaville.dokosmarshall.org> Reply-To: mail@christianmoe.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:45663) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RH9SL-00079f-Mj for emacs-orgmode@gnu.org; Fri, 21 Oct 2011 03:23:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RH9SK-00046H-LX for emacs-orgmode@gnu.org; Fri, 21 Oct 2011 03:23:53 -0400 Received: from b1.hitrost.net ([91.185.211.67]:54040) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RH9SK-00045k-BS for emacs-orgmode@gnu.org; Fri, 21 Oct 2011 03:23:52 -0400 In-Reply-To: <8895.1319165867@alphaville.dokosmarshall.org> 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: nicholas.dokos@hp.com Cc: Sebastien Vauban , emacs-orgmode@gnu.org > I disagree with Tom on [1]: it should clearly be "srcname", in analogy > to #+tblname - and also so I don't have to change my files :-} (but see > my question about tblname below). I'll have to change my files, either way. The price one pays for inconsistency. But as I've recently learned from Carsten, it should be a one-liner in Perl. :-) For the sake of analogy, I'll cast my vote for SRCNAME, even if SOURCE is more aesthetically pleasing. > > I agree on [2] "call". +1 > > I'm confused by [3] so I will say nothing for now, except to ask some > questions: are we talking about what a human would use to label a piece > of data for consumption by a block (including perhaps the future > possibilities of lists and paragraphs that Tom brought up)? what babel > would use to label a results block (possibly so that it could be > consumed by another block in a chain)? both? would that mean > that #+tblname would go the way of the dodo and that tables would be > labelled with #+data (or #+object or whatever else we come up with)? +1 (Confused, too) I wasn't even aware of #+DATA. Does it do anything TBLNAME and SRCNAME don't? A reason to keep TBLNAME is that it's also used by the spreadsheet remote references. If Babel looked for DATA instead, a table that is both a remote reference for another spreadsheet and a data source for a src block would need both TBLNAME and DATA, which seems redundant. As for labeling lists and paragraphs, I recall from the list that Nicolas Goaziou is working on a generalized way to set captions, labels and attributes for various kinds of Org block, as is possible now for tables and images. I thought that sounded promising. I don't know if he planned for block names, too (currently we have tblname but no imgname), but that could make sense. In which case it might be a good idea to coordinate.