From mboxrd@z Thu Jan 1 00:00:00 1970 From: tsd@tsdye.com (Thomas S. Dye) Subject: Re: [RFC] Standardized code block keywords Date: Fri, 21 Oct 2011 09:10:27 -1000 Message-ID: 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> <4EA11EA7.7020501@christianmoe.com> <87wrby5mus.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([140.186.70.92]:36435) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RHKUF-0004vs-Dn for emacs-orgmode@gnu.org; Fri, 21 Oct 2011 15:10:36 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RHKUD-0001yY-BD for emacs-orgmode@gnu.org; Fri, 21 Oct 2011 15:10:35 -0400 Received: from oproxy5-pub.bluehost.com ([67.222.38.55]:52721) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1RHKUC-0001yI-UF for emacs-orgmode@gnu.org; Fri, 21 Oct 2011 15:10:33 -0400 In-Reply-To: <87wrby5mus.fsf@gmail.com> (Eric Schulte's message of "Fri, 21 Oct 2011 10:12:14 -0600") 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: Eric Schulte Cc: Sebastien Vauban , nicholas.dokos@hp.com, emacs-orgmode@gnu.org, mail@christianmoe.com Eric Schulte writes: >>> 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) >> > > well, I guess it is good that this discussion has begun if only to clear > up this lingering uncertainty. > >> >> I wasn't even aware of #+DATA. Does it do anything TBLNAME and SRCNAME >> don't? >> > > from the prospective of code blocks it is exactly synonymous with > tblname. Srcname is different in that it labels code blocks. > >> >> 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. >> > > agreed, I'm thinking that tblname will at least remain an option no > matter what decision is made. > >> >> 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. >> > > Agreed, I was not aware of this work. Thanks for sharing. In this vein > I would like to voice my desire to be able to add captions to code > blocks, the lack of this feature has bitten me in the past. Hi Eric, For LaTeX export, the listings package has support for code block captions. hth, Tom -- Thomas S. Dye http://www.tsdye.com