From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric S Fraga Subject: Re: :noweb header argument Date: Tue, 10 Jan 2012 21:04:55 +0000 Message-ID: <877h0zjmko.fsf@ucl.ac.uk> References: <801ur8rnjg.fsf@somewhere.org> <87ty43ik2y.fsf@gmx.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:49785) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rkisc-0007U4-Su for emacs-orgmode@gnu.org; Tue, 10 Jan 2012 16:05:15 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Rkisb-0001Hg-OK for emacs-orgmode@gnu.org; Tue, 10 Jan 2012 16:05:14 -0500 Received: from vscane-b.ucl.ac.uk ([144.82.108.141]:59817) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Rkisb-0001HE-IT for emacs-orgmode@gnu.org; Tue, 10 Jan 2012 16:05:13 -0500 In-Reply-To: <87ty43ik2y.fsf@gmx.com> (Eric Schulte's message of "Tue, 10 Jan 2012 09:44:05 -0700") 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 , emacs-orgmode@gnu.org Eric Schulte writes: > tsd@tsdye.com (Thomas S. Dye) writes: [...] >> Alternatively for LaTeX, some way to wrap exported code blocks in a >> \begin{listing} ... \end{listing} environment, complete with caption and >> label. This way the code block name could appear in the caption, and >> with \listoflistings, in the document frontmatter as well. >> > > As I recall this was originally implemented and then later removed > because it was causing more confusion and problems than it was worth. I > hope it hasn't crossed the line of existence more than once. At some > point it should be placed behind a user-customizable variable, > preferably something like `org-babel-export-code-format' which defaults > to something like "%code" but could be augmented to something like > "Block Name: *%name*\n %code". It is not immediately clear if such a > variable should have different values for different export backends or > (likely preferable) should expand into Org-mode text *before* export. There is some precedence for having target specific customisations, even if that is not a pretty approach. As an example that has come up recently, and one that I was just using a few minutes ago (!), we have ,----[ C-h v org-export-latex-timestamp-markup RET ] | org-export-latex-timestamp-markup is a variable defined in `org-latex.el'. | Its value is "\\hfill Action created or updated: %s" | Original value was "\\textit{%s}" |=20 | Documentation: | A printf format string to be applied to time stamps. |=20 | You can customize this variable. |=20 | [back] `---- Although I can see the benefit of a generic intermediate step, I am of the belief that target specific markups are going to be more powerful and likely more useful... Just my two =C2=A2. --=20 : Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 24.0.92.1 : using Org-mode version 7.8.03 (release_7.8.03.73.gd2b3d)